[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: |
Tue, 10 Nov 2020 21:30:03 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (x86_64-pc-linux-gnu) |
> 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.
Thanks for pointing to emacs-orgmode@gnu.org. Surprisingly, I see
my bug report on the Org list, maybe this is because I added
Package: emacs,org-mode
to the bug report. Since there is no reply to my bug report, I pushed
the fix to Emacs master as commit 79d04ae13f. Thanks to Kyle
we don't have to worry about the commit arriving to the Org repo.
Whereas it seems fine to fix bugs in the Emacs repo, submitting
patches for new features indeed needs to be discussed on the Org list.
- 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, 2020/11/09
- bug#32676: Updating Org for 27.2, Kyle Meyer, 2020/11/09
- bug#32676: Updating Org for 27.2,
Juri Linkov <=
- bug#32676: Updating Org for 27.2, Glenn Morris, 2020/11/10