GNU bug report logs -
#61489
[PATCH 1/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵
Previous Next
Full log
View this message in rfc822 format
On Tue, 2023-02-14 at 11:22 +0300, Konstantin Kharlamov wrote:
> 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 <at> 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 <at> 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.
Oh, sorry, I'm being stupid. Right, there's no report will be created because I send the series to the existing report. Sorry.
This bug report was last modified 2 years and 176 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.