From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] git send-email: include [anything]-by: signatures
Date: Tue, 3 Sep 2013 11:44:54 +0300 [thread overview]
Message-ID: <20130903084454.GC18901@redhat.com> (raw)
In-Reply-To: <20130903063535.GA3608@sigill.intra.peff.net>
On Tue, Sep 03, 2013 at 02:35:35AM -0400, Jeff King wrote:
> On Sat, Aug 31, 2013 at 10:22:50PM +0300, Michael S. Tsirkin wrote:
>
> > On Mon, Aug 26, 2013 at 07:57:47PM +0300, Michael S. Tsirkin wrote:
> > > Consider [anything]-by: a valid signature.
> > > This includes Tested-by: Acked-by: Reviewed-by: etc.
> > >
> > > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> >
> > Ping.
> > Any opinion on whether this change is acceptable?
>
> I was left confused by your commit message, as it wasn't clear to me
> what a "signature" is. But the point of it seems to be that people
> mention others in commit messages using "X-by:" pseudo-headers besides
> "signed-off-by", and you want to cc them along with the usual S-O-B.
>
> That seems like a reasonable goal, but I have two concerns.
>
> One, I would think the utility of this would be per-project, depending
> on what sorts of things people in a particular project put in
> pseudo-headers. Grepping the kernel history shows that most X-by
> headers have a person on the right-hand side, though quite often it is
> not a valid email address (on the other hand, quite a few s-o-b lines in
> the kernel do not have a valid email).
>
> And two, the existing options for enabling/disabling this code all
> explicitly mention signed-off-by, which becomes awkward. You did not
> update the documentation in your patch, but I think you would end up
> having to explain that "--supress-cc=sob" and "--signed-off-by-cc"
> really mean "all pseudo-header lines ending in -by".
>
> So I think it might be a nicer approach to introduce a new "suppress-cc"
> class that means "all pseudo-header tokens ending in -by" or similar.
> We might even want the new behavior on by default, but it would at least
> give the user an escape hatch if their project generates a lot of false
> positives.
>
> -Peff
I guess there's always cccmd, no?
--
MST
next prev parent reply other threads:[~2013-09-03 8:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 16:57 [PATCH] git send-email: include [anything]-by: signatures Michael S. Tsirkin
2013-08-31 19:22 ` Michael S. Tsirkin
2013-09-03 6:35 ` Jeff King
2013-09-03 8:44 ` Michael S. Tsirkin [this message]
2013-09-03 17:06 ` Junio C Hamano
2013-09-03 21:01 ` Michael S. Tsirkin
2013-09-03 21:03 ` Jeff King
2013-09-03 21:24 ` Michael S. Tsirkin
2013-09-03 21:39 ` Junio C Hamano
2013-09-04 8:09 ` Michael S. Tsirkin
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=20130903084454.GC18901@redhat.com \
--to=mst@redhat.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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).