# [PATCH] fix git format-patch --cc=<email> format

5 messages from 2009-02-28 to 2009-03-01. Participants: Peng Tao, Jay Soffian, Junio C Hamano, Jeff King.
Thread: https://gitlist.dev/t/18063

## Peng Tao, 2009-02-28 12:42

Subject: [PATCH] fix git format-patch --cc=<email> format
Message-ID: <1235824944-4967-1-git-send-email-bergwolf@gmail.com>
URL: https://gitlist.dev/e/1235824944-4967-1-git-send-email-bergwolf%40gmail.com

```
If there are multiple --cc=<email> arguments, git format-patch will generate
patches with cc lines like:
  Cc: <email>,
      <email>
which git send-email fails to parse.
git send-email only accept formats like:
  Cc: <email>
  Cc: <email>
So change git format-patch to generate patches in a proper format.

Signed-off-by: Peng Tao <bergwolf@gmail.com>
---
 builtin-log.c |    6 +-----
 1 files changed, 1 insertions(+), 5 deletions(-)

diff --git a/builtin-log.c b/builtin-log.c
index 60f8dd8..22bb6b6 100644
--- a/builtin-log.c
+++ b/builtin-log.c
@@ -907,13 +907,9 @@ int cmd_format_patch(int argc, const char **argv, const char *prefix)
 	}
 
 	if (extra_cc_nr)
-		strbuf_addstr(&buf, "Cc: ");
 	for (i = 0; i < extra_cc_nr; i++) {
-		if (i)
-			strbuf_addstr(&buf, "    ");
+		strbuf_addstr(&buf, "Cc: ");
 		strbuf_addstr(&buf, extra_cc[i]);
-		if (i + 1 < extra_cc_nr)
-			strbuf_addch(&buf, ',');
 		strbuf_addch(&buf, '\n');
 	}
 

```

## Jay Soffian, 2009-02-28 16:15

Subject: Re: [PATCH] fix git format-patch --cc=<email> format
Message-ID: <76718490902280815if1c3fa7o790112b410d52224@mail.gmail.com>
URL: https://gitlist.dev/e/76718490902280815if1c3fa7o790112b410d52224%40mail.gmail.com
In-Reply-To: <1235824944-4967-1-git-send-email-bergwolf@gmail.com>

```
On Sat, Feb 28, 2009 at 7:42 AM, Peng Tao <bergwolf@gmail.com> wrote:
> If there are multiple --cc=<email> arguments, git format-patch will generate
> patches with cc lines like:
>  Cc: <email>,
>      <email>
> which git send-email fails to parse.
> git send-email only accept formats like:
>  Cc: <email>
>  Cc: <email>
> So change git format-patch to generate patches in a proper format.

This is fixed in next, but we fixed send-email instead to handle the
messages that format-patch generates, as they should be valid.

j.

```

## Junio C Hamano, 2009-02-28 17:29

Subject: Re: [PATCH] fix git format-patch --cc=<email> format
Message-ID: <7vy6vqfp0p.fsf@gitster.siamese.dyndns.org>
URL: https://gitlist.dev/e/7vy6vqfp0p.fsf%40gitster.siamese.dyndns.org
In-Reply-To: <76718490902280815if1c3fa7o790112b410d52224@mail.gmail.com>

```
Jay Soffian <jaysoffian@gmail.com> writes:

> On Sat, Feb 28, 2009 at 7:42 AM, Peng Tao <bergwolf@gmail.com> wrote:
>> If there are multiple --cc=<email> arguments, git format-patch will generate
>> patches with cc lines like:
>>  Cc: <email>,
>>      <email>
>> which git send-email fails to parse.
>> git send-email only accept formats like:
>>  Cc: <email>
>>  Cc: <email>
>> So change git format-patch to generate patches in a proper format.
>
> This is fixed in next, but we fixed send-email instead to handle the
> messages that format-patch generates, as they should be valid.

Per RFC2822 3.6 (pp 19-20), "cc" is to appear at most once (same is true
for "to" and "bcc").  I think fix to format-patch is necessary regardless
of what send-email does.

```

## Jeff King, 2009-03-01 01:01

Subject: Re: [PATCH] fix git format-patch --cc=<email> format
Message-ID: <20090301010116.GA20255@coredump.intra.peff.net>
URL: https://gitlist.dev/e/20090301010116.GA20255%40coredump.intra.peff.net
In-Reply-To: <7vy6vqfp0p.fsf@gitster.siamese.dyndns.org>

```
On Sat, Feb 28, 2009 at 09:29:58AM -0800, Junio C Hamano wrote:

> >> If there are multiple --cc=<email> arguments, git format-patch will generate
> >> patches with cc lines like:
> >>  Cc: <email>,
> >>      <email>
> >> which git send-email fails to parse.
> >> git send-email only accept formats like:
> >>  Cc: <email>
> >>  Cc: <email>
> >> So change git format-patch to generate patches in a proper format.
> >
> > This is fixed in next, but we fixed send-email instead to handle the
> > messages that format-patch generates, as they should be valid.
> 
> Per RFC2822 3.6 (pp 19-20), "cc" is to appear at most once (same is true
> for "to" and "bcc").  I think fix to format-patch is necessary regardless
> of what send-email does.

Then isn't the current format-patch output (folding the cc over
multiple lines) correct, and the patch (outputting multiple cc headers)
wrong?

-Peff

```

## Junio C Hamano, 2009-03-01 02:24

Subject: Re: [PATCH] fix git format-patch --cc=<email> format
Message-ID: <7vk57aasjx.fsf@gitster.siamese.dyndns.org>
URL: https://gitlist.dev/e/7vk57aasjx.fsf%40gitster.siamese.dyndns.org
In-Reply-To: <20090301010116.GA20255@coredump.intra.peff.net>

```
Jeff King <peff@peff.net> writes:

> On Sat, Feb 28, 2009 at 09:29:58AM -0800, Junio C Hamano wrote:
>
>> >> If there are multiple --cc=<email> arguments, git format-patch will generate
>> >> patches with cc lines like:
>> >>  Cc: <email>,
>> >>      <email>
>> >> which git send-email fails to parse.
>> >> git send-email only accept formats like:
>> >>  Cc: <email>
>> >>  Cc: <email>
>> >> So change git format-patch to generate patches in a proper format.
>> >
>> > This is fixed in next, but we fixed send-email instead to handle the
>> > messages that format-patch generates, as they should be valid.
>> 
>> Per RFC2822 3.6 (pp 19-20), "cc" is to appear at most once (same is true
>> for "to" and "bcc").  I think fix to format-patch is necessary regardless
>> of what send-email does.
>
> Then isn't the current format-patch output (folding the cc over
> multiple lines) correct, and the patch (outputting multiple cc headers)
> wrong?

Ahh, sorry I misread what the commit message was saying and the patch was
doing.

```