[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#32676: Updating Org for 27.2
|
From: |
Kévin Le Gouguec |
|
Subject: |
bug#32676: Updating Org for 27.2 |
|
Date: |
Mon, 09 Nov 2020 13:17:14 +0100 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
Juri Linkov <juri@linkov.net> writes:
> Do you know if the synchronization process will override the changes
> made in master? If I fix an issue in bug#44524 and will commit the fix
> to Emacs master in the subdir emacs/lisp/org, won't the synchronization
> process of the recent Org version override my fix?
The document I referred to covers this situation (§ Backporting changes
from upstream Emacs), but I don't know if there are automated checks in
place to make sure no commits are missed.
IIUC, Org maintainers prefer for changes to be submitted to
emacs-orgmode@gnu.org; they only occasionally dive into
bug-gnu-emacs@gnu.org to look for open Org issues.
- bug#32676: [PATCH] Add option to highlight the 'next-error' error message, Juri Linkov, 2020/11/05
- bug#32676: [PATCH] Add option to highlight the 'next-error' error message, Kévin Le Gouguec, 2020/11/05
- bug#32676: [PATCH] Add option to highlight the 'next-error' error message, Juri Linkov, 2020/11/06
- bug#32676: Updating Org for 27.2 (was: bug#32676: [PATCH] Add option to highlight the 'next-error' error message), Kévin Le Gouguec, 2020/11/06
- bug#32676: Updating Org for 27.2, Juri Linkov, 2020/11/09
- bug#32676: Updating Org for 27.2,
Kévin Le Gouguec <=
- bug#32676: Updating Org for 27.2, Kyle Meyer, 2020/11/09
- bug#32676: Updating Org for 27.2, Juri Linkov, 2020/11/10
- bug#32676: Updating Org for 27.2, Glenn Morris, 2020/11/10