[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#61489: Open a bug report with git-send-email (was: bug#61489: Acknow
From: |
Kévin Le Gouguec |
Subject: |
bug#61489: Open a bug report with git-send-email (was: bug#61489: Acknowledgement ([PATCH 1/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵)) |
Date: |
Wed, 15 Feb 2023 08:03:56 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Robert Pluim <rpluim@gmail.com>
>> Cc: Eli Zaretskii <eliz@gnu.org>, 61489@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@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@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.
- bug#61490: [PATCH 0/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵, Konstantin Kharlamov, 2023/02/13
- bug#61489: [PATCH 1/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵, Konstantin Kharlamov, 2023/02/13
- Message not available
- bug#61489: Acknowledgement ([PATCH 1/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵), Konstantin Kharlamov, 2023/02/13
- bug#61489: Acknowledgement ([PATCH 1/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵), Eli Zaretskii, 2023/02/13
- bug#61489: Acknowledgement ([PATCH 1/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵), Konstantin Kharlamov, 2023/02/14
- bug#61489: Acknowledgement ([PATCH 1/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵), Konstantin Kharlamov, 2023/02/14
- bug#61489: Acknowledgement ([PATCH 1/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵), Robert Pluim, 2023/02/14
- bug#61489: Acknowledgement ([PATCH 1/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵), Konstantin Kharlamov, 2023/02/14
- bug#61489: Acknowledgement ([PATCH 1/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵), Konstantin Kharlamov, 2023/02/14
- bug#61489: Acknowledgement ([PATCH 1/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵), Eli Zaretskii, 2023/02/14
- bug#61489: Open a bug report with git-send-email (was: bug#61489: Acknowledgement ([PATCH 1/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵)),
Kévin Le Gouguec <=
bug#61489: [PATCH 1/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵, Ihor Radchenko, 2023/02/13
bug#61489: [PATCH v2] Increase BLOCK_ALIGN from 1024 to 32768, Konstantin Kharlamov, 2023/02/16
- bug#61490: [PATCH v2] Increase BLOCK_ALIGN from 1024 to 32768, Konstantin Kharlamov, 2023/02/23
- bug#61490: bug#61489: [PATCH v2] Increase BLOCK_ALIGN from 1024 to 32768, Robert Pluim, 2023/02/23
- bug#61490: bug#61489: [PATCH v2] Increase BLOCK_ALIGN from 1024 to 32768, Konstantin Kharlamov, 2023/02/23
- bug#61490: bug#61489: [PATCH v2] Increase BLOCK_ALIGN from 1024 to 32768, Robert Pluim, 2023/02/23
- bug#61490: bug#61489: [PATCH v2] Increase BLOCK_ALIGN from 1024 to 32768, Konstantin Kharlamov, 2023/02/23
- bug#61489: [PATCH v2] Increase BLOCK_ALIGN from 1024 to 32768, Robert Pluim, 2023/02/23
bug#61489: bug#61490: bug#61489: [PATCH v2] Increase BLOCK_ALIGN from 1024 to 32768, Eli Zaretskii, 2023/02/23
bug#61489: bug#61490: bug#61489: [PATCH v2] Increase BLOCK_ALIGN from 1024 to 32768, Robert Pluim, 2023/02/24