All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] git send-email: include [anything]-by: signatures
Date: Wed, 4 Sep 2013 00:24:32 +0300	[thread overview]
Message-ID: <20130903212432.GC24480@redhat.com> (raw)
In-Reply-To: <20130903210352.GA27344@sigill.intra.peff.net>

On Tue, Sep 03, 2013 at 05:03:52PM -0400, Jeff King wrote:
> On Wed, Sep 04, 2013 at 12:01:49AM +0300, Michael S. Tsirkin wrote:
> 
> > > The question of course is the first point Peff raised.  I am not
> > > sure offhand what the right per-project customization interface
> > > would be.  A starting point might be something like:
> > > 
> > > 	--cc-trailer=signed-off-by,acked-by,reviewed-by
> > 
> > tested-by, reported-by ...
> 
> Yeah, I think having the list customizable is nice, but not allowing
> some pattern matching seems unfriendly, as it requires the user to
> enumerate a potentially long list.
> 
> > > 	--cc-trailer='*-by'
> > > 
> > > and an obvious configuration variable that gives the default for it.
> > > That would eventually allow us not to special case any fixed set of
> > > trailers like S-o-b like the current code does, which would be a big
> > > plus.
> > 
> > What bothers me is that git normally uses gawk based patterns,
> > but send-email is in perl so it has a different syntax for regexp.
> > What do you suggest?  Make a small binary to do the matching for us?
> 
> Would fnmatch-style globbing (like "*-by") be enough? That should be
> easy to do in perl.
> 
> -Peff

If you mean only support * - that would be easy.
Once you get into bracket expressions it gets messy quickly
http://pubs.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap09.html#tag_09_03_05

-- 
MST

  reply	other threads:[~2013-09-03 21:23 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
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 [this message]
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=20130903212432.GC24480@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 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.