git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lodato <lodatom@gmail.com>
To: Craig de Stigter <craig.destigter@koordinates.com>
Cc: git@vger.kernel.org
Subject: Re: git-svn fails with non-alphanumeric SVN authors
Date: Wed, 24 Feb 2010 21:52:30 -0500	[thread overview]
Message-ID: <ca433831002241852x41af821dm5549dd602d5b89e7@mail.gmail.com> (raw)
In-Reply-To: <e260aad41002241247r180d5477kd18f5cbee8109634@mail.gmail.com>

On Wed, Feb 24, 2010 at 3:47 PM, Craig de Stigter
<craig.destigter@koordinates.com> wrote:
> I'm trying to use git-svn to move our subversion to git. Some of the
> authors in our SVN repository are x.509 identifiers, so my authors
> file has some entries like this:
>   /C=NZ/ST=New Zealand/L=Auckland/O=Koordinates
> Ltd/OU=IS/CN=cdestigter = Craig de Stigter
> <craig.destigter@koordinates.com>
>
> git-svn doesn't like that - it fails saying:
>   Author: /C=NZ/ST=New Zealand/L=Auckland/O=Koordinates
> Ltd/OU=IS/CN=cdestigter not defined in ./authors.txt file
>
> I presume it is choking on either the spaces or the '=' characters in
> the SVN username?

Yes.  The --authors-file option reads the name up to the first equals
sign, which causes a problem for the X.509 identifiers.  I had this
exact problem, which is why I implemented --authors-prog. [1]  In my
case, I could compute the username and email address from the X.509
id, so I didn't have to list them all out.  Perhaps you can use this
to solve your problem?  Even if you can't compute the name directly
from the X.509 ID, you could implement your own lookup in a script.

[1] http://www.spinics.net/lists/git/msg103524.html

      reply	other threads:[~2010-02-25  2:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24 20:47 git-svn fails with non-alphanumeric SVN authors Craig de Stigter
2010-02-25  2:52 ` Mark Lodato [this message]

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=ca433831002241852x41af821dm5549dd602d5b89e7@mail.gmail.com \
    --to=lodatom@gmail.com \
    --cc=craig.destigter@koordinates.com \
    --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).