mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Christian Couder <>
To: Taylor Blau <>
Cc: Siddharth Asthana <>,,,
Subject: Re: [PATCH] doc/cat-file: allow --use-mailmap for --batch options
Date: Sun, 30 Oct 2022 08:06:19 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <Y11rnKwuR0q47ngq@nand.local>

Hi Taylor,

On Sat, Oct 29, 2022 at 8:06 PM Taylor Blau <> wrote:
> Hi Siddharth,
> On Sat, Oct 29, 2022 at 02:55:13PM +0530, Siddharth Asthana wrote:
> > This patch was previously sent as the first patch of a 3 patch series for
> > adding the mailmap support in git cat-file options:
> >
> Why was this split off from the original series? I don't have a problem
> queueing the two topics independently, but an explanation of how the two
> interact would be appreciated.

I think it was split off from the original series because it's a
documentation fix that could hopefully have graduated faster, and
could perhaps have made it into v2.38.0. Or perhaps it could make it
in v2.38.2 if such a bug fix release is made.

> E.g., does one depend on the other? Are they independent and can be
> merged at will? Should the integrator expect merge conflicts?

The other patch series has some code changes that are independent, but
the documentation changes it makes should probably go on top of this.


  reply	other threads:[~2022-10-30  7:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23 19:35 [PATCH] doc/cat-file: allow --use-mailmap for --batch options Siddharth Asthana
2022-09-24 14:49 ` Christian Couder
2022-09-26  9:14 ` Siddharth Asthana
2022-09-26 14:11   ` John Cai
2022-10-21 10:32     ` Siddharth Asthana
2022-10-21 10:34 ` Siddharth Asthana
2022-10-21 18:56   ` Junio C Hamano
2022-10-29  9:25 ` Siddharth Asthana
2022-10-29 18:06   ` Taylor Blau
2022-10-30  7:06     ` Christian Couder [this message]
2022-10-30 18:07       ` Taylor Blau
2022-10-31 10:54   ` Christian Couder
2022-11-13 21:26     ` Siddharth Asthana

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:

  List information:

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

  git send-email \ \ \ \ \ \ \ \

* 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

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).