GNU bug report logs - #68375
29.1; lispref documentation fixes

Previous Next

Full log

View this message in rfc822 format

From: Stephen Berman <stephen.berman <at> gmx.net>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 68375 <at> debbugs.gnu.org, manphiz <at> gmail.com
Subject: bug#68375: 29.1; lispref documentation fixes
Date: Thu, 11 Jan 2024 17:39:16 +0100

On Thu, 11 Jan 2024 17:33:17 +0200 Eli Zaretskii <eliz <at> gnu.org> wrote:

>> From: Stephen Berman <stephen.berman <at> gmx.net>
>> Cc: 68375 <at> debbugs.gnu.org,  manphiz <at> gmail.com
>> Date: Thu, 11 Jan 2024 16:18:48 +0100
[...]
>> >> I thought I'd save you some work by installing the patch myself,
>> >> which I just did, but unfortunately to master instead of emacs-29
>> >> (and also forgot to add the bug number).  Should I revert it and
>> >> install to the release branch?  Sorry for the trouble.
>> >
>> > You could have simply cherry-picked it to emacs-29.
>>
>> Is it possible to do that with VC?
>
> No, not that I know of.

Pity.

>> I didn't find the term in the source code, only in
>> admin/notes/git-workflow, which only shows the git command (and says
>> to "add 'Backport:' to the commit string", which is another
>> attention block I could well stumble over...).
>
> If you cherry-pick with the -x option, gitmerge.el will recognize the
> cherry-picks automatically, and there's no need for the "backport"
> indication.

Ah, ok.  But then shouldn't that directive be removed from the text,
since the example invocation has the -x option?  Anyway, hopefully I'll
be attentive enough in future to avoid needing to cherry-pick a commit
due to mistakenly installing a change to the wrong branch.

Steve Berman

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.