git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Andy Whitcroft <apw@shadowen.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] svnimport add support for parsing From lines for author
Date: Tue, 26 Sep 2006 22:34:41 -0700	[thread overview]
Message-ID: <7vfyedj2j2.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <4518DC11.5050806@shadowen.org> (Andy Whitcroft's message of "Tue, 26 Sep 2006 08:51:45 +0100")

Andy Whitcroft <apw@shadowen.org> writes:

>>> Now that we have support for parsing Signed-off-by: for author
>>> information it makes sense to handle From: as well.
>> 
>> I take that you are referring to Sasha's change in ae35b304; I
>> asked for actual svn users for ACK/NACK but I did not hear any.
>> Can I understand that you use svnimport for real projects and
>> are happy with Sasha's change? --- that would be an ack that
>> would help me sleep better ;-).
>
> Heh.  Yeah I am tracking a small SVN repository which is using the
> kernel DCO.  we have From:/S-o-b: much as akpm uses in -mm.  This was
> the result of seeing that change and wanting to see if it would pick up
> our sign-offs.  It only seemed deficient in From: handling :).  It seems
> to work well in practice for me.

Thanks.

>> I also wonder instead of piling up custom flags if it is better
>> to let match-and-extract pattern be specified from the command
>> line.
>
> I did look at reusing the -S flag, such that -S would be S-o-b: handling
> and -SS would be S-o-b: and From:, but this script is currently using
> the old getopt implementation which doesn't record repeats.
>
> So you're proposing something more like:
>
>     git svn-import -S "Signed-off-by:" -S "From:" ...
>
> Again, we'll have to update the options handling to get that kind of
> behaviour.  How would you feel about -SS in this context.

It was more of an idle speculation than a serious proposal.  I
do not think there are too many different ways to record the
authorship information, so having just two hardwired patterns -F
and -S would be sufficient.  If there were, then string of -S
options that specify the header-looking strings or match
patterns would have made more sense.

  reply	other threads:[~2006-09-27  5:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-25 11:08 [PATCH] svnimport add support for parsing From lines for author Andy Whitcroft
2006-09-26  5:08 ` Junio C Hamano
2006-09-26  7:51   ` Andy Whitcroft
2006-09-27  5:34     ` Junio C Hamano [this message]
2006-09-28 10:58       ` Andy Whitcroft
2006-09-28 16:10         ` 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=7vfyedj2j2.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=apw@shadowen.org \
    --cc=git@vger.kernel.org \
    /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).