GNU bug report logs - #15361
git send-email creates one report per patch

Previous Next

Full log

Message #8 received at 15361 <at> debbugs.gnu.org (full text, mbox):

From: Jim Meyering <jim <at> meyering.net>
To: Glenn Morris <rgm <at> gnu.org>
Cc: 15361 <at> debbugs.gnu.org
Subject: Re: bug#15361: git send-email creates one report per patch
Date: Mon, 23 Sep 2013 07:42:35 -0700

On Thu, Sep 12, 2013 at 1:11 PM, Glenn Morris <rgm <at> gnu.org> wrote:
> Package: debbugs.gnu.org
>
> If you send a collection of patches to bug-foo via git send-email,
> it creates one report per patch. Here's why:
...

Hi Glenn,
Doesn't git send-email's --in-reply-to option solve this problem?

       --in-reply-to=<identifier>
           Make the first mail (or all the mails with --no-thread) appear as a
           reply to the given Message-Id, which avoids breaking threads to
           provide a new patch series. The second and subsequent emails will
           be sent as replies according to the --[no]-chain-reply-to setting.

           So for example when --thread and --no-chain-reply-to are specified,
           the second and subsequent patches will be replies to the first one
           like in the illustration below where [PATCH v2 0/3] is in reply to
           [PATCH 0/2]:

               [PATCH 0/2] Here is what I did...
                 [PATCH 1/2] Clean up and tests
                 [PATCH 2/2] Implementation
                 [PATCH v2 0/3] Here is a reroll
                   [PATCH v2 1/3] Clean up
                   [PATCH v2 2/3] New tests
                   [PATCH v2 3/3] Implementation

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.