GNU bug report logs -
#61489
[PATCH 1/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵
Previous Next
Full log
Message #35 received at 61489 <at> debbugs.gnu.org (full text, mbox):
Eli Zaretskii <eliz <at> gnu.org> writes:
>> From: Robert Pluim <rpluim <at> gmail.com>
>> Cc: Eli Zaretskii <eliz <at> gnu.org>, 61489 <at> debbugs.gnu.org
>> Date: Tue, 14 Feb 2023 09:20:58 +0100
>>
>> >>>>> On Tue, 14 Feb 2023 09:56:19 +0300, Konstantin Kharlamov
>> <hi-angel <at> yandex.ru> said:
>>
>> >> Thank you. But, how one sends a patch series then?
>>
>> You send your cover letter to bug-gnu-emacs, which creates a bug
>> <bugnumber>. You then send the rest of the series to
>> <bugnumber>@debbugs.gnu.org (for extra credit, you put the bug number
>> in the commit message before doing this).
>
> Alternatively, send all of the patches in a single email message as
> attachments, then you don't need to wait for the bug tracker to
> allocate a number. Whether this is convenient enough for you depends
> on your workflows vis-a-vis Git and "git format-patch", and also what
> is your MUA and how it is configured.
See e.g. bug#48592 for an example of Robert's procedure (modulo amending
the commit messages with the bug number):
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=48592
https://yhetil.org/emacs-bugs/20210522202519.32549-1-jonas <at> bernoul.li/
GUIX documents this in more detail:
https://guix.gnu.org/manual/en/html_node/Sending-a-Patch-Series.html#Multiple-Patches-1
IIUC we have bug#15361 open to make debbugs understand this kind of
submission without this workaround.
This bug report was last modified 2 years and 175 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.