git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Rast <trast@student.ethz.ch>
To: Jay Soffian <jaysoffian@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH v3] send-email: --suppress-cc improvements
Date: Sat, 14 Feb 2009 23:21:11 +0100	[thread overview]
Message-ID: <200902142321.22904.trast@student.ethz.ch> (raw)
In-Reply-To: <1234631186-10179-1-git-send-email-trast@student.ethz.ch>

[-- Attachment #1: Type: text/plain, Size: 1259 bytes --]

I just noticed that I lost the comments after '---' due to repeated
format-patch'ing, so here goes:

Thomas Rast wrote:
> From: Jay Soffian <jaysoffian@gmail.com>
> 
> Since 6564828 (git-send-email: Generalize auto-cc recipient
> mechanism., 2007-12-25) we can suppress automatic Cc generation
> separately for each of the possible address sources.  However,
> --suppress-cc=sob suppressed both SOB lines and body (but not header)
> Cc lines, contrary to the name.
> 
> Change --suppress-cc=sob to mean only SOB lines, and add separate
> choices 'bodycc' (body Cc lines) and 'body' (both 'sob' and 'bodycc').
> The option --no-signed-off-by-cc now acts like --suppress-cc=sob,
> which is not backwards compatible but matches the name of the option.
> 
> Also update the documentation and add a few tests.
> 
> Signed-off-by: Jay Soffian <jaysoffian@gmail.com>
> Signed-off-by: Thomas Rast <trast@student.ethz.ch>
> ---

I tried to address Junio's comments, mostly by reformatting the docs
and expanding the tests, but also changing the handling of 'body' in
the code.  I also edited the patch message to my liking.

Of course your SOB above is now forged, so you'll have to ack it.

-- 
Thomas Rast
trast@{inf,student}.ethz.ch

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2009-02-14 22:23 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-13 23:05 [PATCH] send-email: handle multiple Cc addresses when reading mbox message Jay Soffian
2009-02-13 23:32 ` Thomas Rast
2009-02-13 23:39   ` Jay Soffian
2009-02-13 23:44     ` Jay Soffian
2009-02-14  3:51   ` Jay Soffian
2009-02-14 16:57     ` Thomas Rast
2009-02-14  3:51   ` [PATCH 1/3] send-email: correct logic error with --suppress-cc=cc Jay Soffian
2009-02-14  6:21     ` [PATCH 1/3 v2] " Jay Soffian
2009-02-14  6:52       ` Junio C Hamano
2009-02-14  7:15         ` Jay Soffian
2009-02-14  7:35           ` Junio C Hamano
2009-02-14  3:51   ` [PATCH 2/3] send-email: don't call unquote_rfc2047 unnecessarily Jay Soffian
2009-02-14  5:50     ` Jay Soffian
2009-02-14  3:51   ` [PATCH 3/3] send-email: --suppress-cc improvements Jay Soffian
2009-02-14  5:37     ` [PATCH 3/3 v2] " Jay Soffian
2009-02-14  6:36       ` Junio C Hamano
2009-02-14 17:06         ` [PATCH v3] " Thomas Rast
2009-02-14 17:06           ` [Interdiff " Thomas Rast
2009-02-14 22:21           ` Thomas Rast [this message]
2009-02-15 10:47             ` [PATCH " Junio C Hamano
2009-02-14  0:31 ` [PATCH] send-email: handle multiple Cc addresses when reading mbox message Jeff King
2009-02-14  0:42   ` Jay Soffian
2009-02-14  3:37     ` Jeff King
2009-02-14  8:16     ` Junio C Hamano

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=200902142321.22904.trast@student.ethz.ch \
    --to=trast@student.ethz.ch \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jaysoffian@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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.
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 NNTP newsgroup(s).