From: Konstantin Kharlamov <hi-angel@yandex.ru>
To: Robert Pluim <rpluim@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 61489@debbugs.gnu.org
Subject: bug#61489: Acknowledgement ([PATCH 1/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵)
Date: Tue, 14 Feb 2023 11:22:49 +0300 [thread overview]
Message-ID: <9fa5c7981f273454f87ddd04b104be857bb7c7d7.camel@yandex.ru> (raw)
In-Reply-To: <87ilg4psid.fsf@gmail.com>
On Tue, 2023-02-14 at 09:20 +0100, Robert Pluim wrote:
> > > > > > On Tue, 14 Feb 2023 09:56:19 +0300, Konstantin Kharlamov
> > > > > > <hi-angel@yandex.ru> said:
>
> Konstantin> On Tue, 2023-02-14 at 09:45 +0300, Konstantin Kharlamov wrote:
> >> On Tue, 2023-02-14 at 05:29 +0200, Eli Zaretskii wrote:
> >> > > From: Konstantin Kharlamov <hi-angel@yandex.ru>
> >> > > Date: Mon, 13 Feb 2023 23:05:21 +0300
> >> > >
> >> > > Idk if it's a feature (bugtracker is an odd way of managing the
> patches in
> >> > > general, so who knows), but for the safe case I'll mention that
> debbugs
> >> > > created
> >> > > for the cover-letter email a separate page bug#61490
> >> >
> >> > You should never change the Subject of a bug report, unless you want
> a
> >> > new bug created by the tracker.
> >>
> >> 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).
But this won't work, because every patch has a different title. So if debbugs
creates a new report per title, this means the problem will still persist.
next prev parent reply other threads:[~2023-02-14 8:22 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 [this message]
2023-02-14 8:29 ` Konstantin Kharlamov
2023-02-14 13:26 ` Eli Zaretskii
2023-02-15 7:03 ` 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
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=9fa5c7981f273454f87ddd04b104be857bb7c7d7.camel@yandex.ru \
--to=hi-angel@yandex.ru \
--cc=61489@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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).