[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#32676: Updating Org for 27.2
From: |
Juri Linkov |
Subject: |
bug#32676: Updating Org for 27.2 |
Date: |
Mon, 09 Nov 2020 11:03:35 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (x86_64-pc-linux-gnu) |
>> Thanks, hope it will be released in Emacs 27.2,
>> also waiting when it will arrive to Emacs 28.
>
> With 9.3.8 (released in September), Org 9.3 is as stable as it well ever
> be, since the maintenance branch is now 9.4. So AFAIK it's "just" a
> matter for Org maintainers to find some time to update Org on the
> emacs-27 branch.
>
> (I filed bug#43268 because I'd love all those bugfixes to land in 27.2;
> I don't know if there's anything more I can do to help. Worg has
> extensive documentation[1] about the synchronization process so I guess
> I could try to make a patch, but I don't know how useful that would be;
> the process seems to have its share of pitfalls[2]…)
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?
- 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 <=
- bug#32676: Updating Org for 27.2, Kévin Le Gouguec, 2020/11/09
- 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