[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#61489: Acknowledgement ([PATCH 1/1] Increase BLOCK_ALIGN from 2¹⁰to
From: |
Konstantin Kharlamov |
Subject: |
bug#61489: Acknowledgement ([PATCH 1/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵) |
Date: |
Tue, 14 Feb 2023 11:29:17 +0300 |
User-agent: |
Evolution 3.46.3 |
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@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.
Oh, sorry, I'm being stupid. Right, there's no report will be created because I
send the series to the existing report. Sorry.
- 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 <=
- 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, 2023/02/15
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