unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Robert Pluim <rpluim@gmail.com>,
	61489@debbugs.gnu.org, hi-angel@yandex.ru
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	[thread overview]
Message-ID: <877cwjpfz7.fsf_-_@gmail.com> (raw)
In-Reply-To: <835yc4e5u7.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 14 Feb 2023 15:26:08 +0200")

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.





  reply	other threads:[~2023-02-15  7:03 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13 20:00 bug#61490: [PATCH 0/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵ Konstantin Kharlamov
2023-02-13 20:00 ` bug#61489: [PATCH 1/1] " Konstantin Kharlamov
     [not found]   ` <handler.61489.B.167631844622733.ack@debbugs.gnu.org>
2023-02-13 20:05     ` bug#61489: Acknowledgement ([PATCH 1/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵) Konstantin Kharlamov
2023-02-14  3:29       ` Eli Zaretskii
2023-02-14  6:45         ` Konstantin Kharlamov
2023-02-14  6:56           ` Konstantin Kharlamov
2023-02-14  8:20             ` Robert Pluim
2023-02-14  8:22               ` Konstantin Kharlamov
2023-02-14  8:29                 ` Konstantin Kharlamov
2023-02-14 13:26               ` Eli Zaretskii
2023-02-15  7:03                 ` Kévin Le Gouguec [this message]
2023-02-13 22:30   ` bug#61489: [PATCH 1/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵ Ihor Radchenko
2023-02-16 15:07   ` bug#61489: [PATCH v2] Increase BLOCK_ALIGN from 1024 to 32768 Konstantin Kharlamov
2023-02-23 15:30     ` Konstantin Kharlamov
2023-02-23 15:49       ` Robert Pluim
2023-02-23 15:53         ` Konstantin Kharlamov
2023-02-23 15:57           ` bug#61490: " Robert Pluim
2023-02-23 16:05             ` Konstantin Kharlamov
2023-02-23 16:34               ` Robert Pluim
2023-02-23 16:41           ` bug#61489: bug#61490: " Eli Zaretskii
2023-02-24 10:50             ` Robert Pluim
2023-02-27 10:30               ` bug#61490: " Konstantin Kharlamov
2023-02-23 16:40         ` Eli Zaretskii
2023-03-04 11:26     ` Eli Zaretskii
2023-03-04 15:00       ` Eli Zaretskii
2023-03-04 15:33         ` Konstantin Kharlamov
2023-03-04 18:58           ` Konstantin Kharlamov
2023-03-04 19:53             ` Eli Zaretskii
2023-03-04 19:58               ` Konstantin Kharlamov
2023-03-05  5:47                 ` Eli Zaretskii
     [not found] ` <handler.61490.B.167631845222751.ack@debbugs.gnu.org>
2023-02-13 20:05   ` bug#61490: Acknowledgement ([PATCH 0/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵) Konstantin Kharlamov
2023-02-16  4:59 ` bug#61490: [PATCH 0/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵ Richard Stallman
2023-02-16  6:46   ` Konstantin Kharlamov
2023-02-16  9:31   ` Gregory Heytings
2023-02-21  5:22     ` bug#61490: [PATCH 0/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵ Richard Stallman
2023-02-16 15:05 ` bug#61490: [PATCH v2] Increase BLOCK_ALIGN from 1024 to 32768 Konstantin Kharlamov
2023-02-16 15:29   ` Robert Pluim
2023-02-16 16:48     ` Konstantin Kharlamov
2023-02-16 17:00       ` Konstantin Kharlamov
2023-02-16 17:02       ` Robert Pluim
2023-03-03 10:44 ` Konstantin Kharlamov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877cwjpfz7.fsf_-_@gmail.com \
    --to=kevin.legouguec@gmail.com \
    --cc=61489@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=hi-angel@yandex.ru \
    --cc=rpluim@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).