git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lodato <lodatom@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org, Eric Wong <normalperson@yhbt.net>,
	Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH v2] git-svn: add --authors-prog option
Date: Fri, 8 May 2009 23:48:39 -0400	[thread overview]
Message-ID: <ca433830905082048u6088a58ai16b1c979ef742f7@mail.gmail.com> (raw)
In-Reply-To: <4A03E2A2.4050303@drmicha.warpmail.net>

On Fri, May 8, 2009 at 3:43 AM, Michael J Gruber
<git@drmicha.warpmail.net> wrote:
> Mark Lodato venit, vidit, dixit 08.05.2009 03:11:
>>  config key: svn.authorsfile
>>
>> +--authors-prog=<filename>::
>> +
>> +If this option is specified, for each SVN committer name that does not
>> +exist in the authors file, the given file is executed with the commiter
>
> s/commiter/committer/
>
> Also, "If..., the given... for each..." may be easier to read.
>
>> +name as the first argument.  The program is expected to return a single
>> +line of the form "Name <email>", which will be logically inserted into the
>
> "be treated as if included in the..."

Will do.

>
> Maybe we want a config key also, just like for the authors file.

Yes, this is a very good idea.  I will figure out how to do this.

> The feature itself looks useful for large user databases. For smaller
> ones one could just as well update the authors file before each fetch by
> dumping the whole db in there (or even conditionally on git svn fetch
> erroring out due to encountering an unknown name).

Right.  This feature will most likely be useful in corporate
environments.  In my case, it is not possible to dump the entire user
database to a file, so this patch is the only solution.  Another
possible use case is where SVN usernames are standardized, e.g. "jdoe"
-> "J Doe <jdoe@example.com>".  Also, using --authors-prog solves the
problem of keeping the authors file up-to-date, if users are regularly
added or deleted.

  reply	other threads:[~2009-05-09  3:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-08  1:11 [PATCH v2] git-svn: add --authors-prog option Mark Lodato
2009-05-08  7:43 ` Michael J Gruber
2009-05-09  3:48   ` Mark Lodato [this message]
2009-05-10  0:35     ` Eric Wong
2009-05-15  1:27       ` [PATCH v3] " Mark Lodato
2009-05-21  8:43         ` Eric Wong
2009-05-21 14:30           ` 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=ca433830905082048u6088a58ai16b1c979ef742f7@mail.gmail.com \
    --to=lodatom@gmail.com \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=normalperson@yhbt.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).