All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git <git@vger.kernel.org>
Subject: Re: git am and duplicate signatures
Date: Tue, 30 Aug 2016 10:26:39 -0700	[thread overview]
Message-ID: <1472577999.5512.107.camel@perches.com> (raw)
In-Reply-To: <xmqqwpiy5haf.fsf@gitster.mtv.corp.google.com>

On Tue, 2016-08-30 at 09:54 -0700, Junio C Hamano wrote:
> Support for more generic footers was supposed to come when the
> "interpret-trailers" topic started, but the author of the topic
> seems to have lost interest before the mechanism has become ready to
> be integrated in the workflow commands like "am", "commit", "rebase"
> etc., which is unfortunate.

I think adding at least an option to git send-email
allowing auto-cc's for all
	"<foo>-by: [name] <address>"
lines in the commit log would be useful.

Today, only "Signed-off-by" and "CC" lines are
added to cc's.

I've always called these lines "<foo>-by:" lines
"signatures", but perhaps there's a better name.

Any preference?

from git send-email --help
       --suppress-cc=<category>
           Specify an additional category of recipients to suppress the
           auto-cc of:

           ·   author will avoid including the patch author

           ·   self will avoid including the sender

           ·   cc will avoid including anyone mentioned in Cc lines in the
               patch header except for self (use self for that).

           ·   bodycc will avoid including anyone mentioned in Cc lines in the
               patch body (commit message) except for self (use self for
               that).

           ·   sob will avoid including anyone mentioned in Signed-off-by
               lines except for self (use self for that).

           ·   cccmd will avoid running the --cc-cmd.

           ·   body is equivalent to sob + bodycc

           ·   all will suppress all auto cc values.
> > 
> > sequencer.c:append_signoff() has a flag for APPEND_SIGNOFF_DEDUP
> Yes, I think this is one of the warts we talked about getting rid of
> but haven't got around to it.  It is there because "format-patch -s"
> was incorrectly written to dedup Signed-off-by: from anywhere in its
> early implementation and to keep the same behaviour.  We should drop
> that flag from append_signoff() function.

  parent reply	other threads:[~2016-08-30 17:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-30 16:12 git am and duplicate signatures Joe Perches
2016-08-30 16:54 ` Junio C Hamano
2016-08-30 17:07   ` Joe Perches
2016-08-30 17:37     ` Junio C Hamano
2016-08-30 17:26   ` Joe Perches [this message]
2016-08-30 17:34     ` Junio C Hamano
2016-08-30 17:41       ` Joe Perches
2016-08-30 17:49         ` Joe Perches
2016-08-30 18:17           ` Junio C Hamano
2016-08-30 18:21             ` Joe Perches
2016-08-30 19:00               ` 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=1472577999.5512.107.camel@perches.com \
    --to=joe@perches.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.