From: Eric Wong <normalperson@yhbt.net>
To: Adrian Wilkins <adrian.wilkins@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: BUG: git-svn does not escape literal backslashes in author names.
Date: Sat, 17 Nov 2007 12:43:48 -0800 [thread overview]
Message-ID: <20071117204348.GA16333@muzzle> (raw)
In-Reply-To: <1213a9470711120628l4ccab632n17635295ec897a2@mail.gmail.com>
Adrian Wilkins <adrian.wilkins@gmail.com> wrote:
> Recently converted a large (11,000+ revisions) repository.
>
> We authenticate against the NT domain controller, so all our revision
> authors are of the form "domain\user". (You can switch off mod_sspi
> reporting the domain part, but I didn't know about this at the time,
> so it continues for historical reasons.)
>
> git-svn treats the literal backslashes in the author names as escapes.
> This leads to authors like
>
> domainkevin
> domain\
> ichard
>
> I know, I should have read the manual and used my "authors" file. Bah.
>
> I'm sure that part of the revision hash in git includes the author
> name... so I guess I'm looking at another multi-day conversion. :-(
git-filter-branch should be able to take care of it. If you find
an invocation that's useful to others, it'd be great to post it
on the list as well :)
> Can I suggest that you make the authors file compulsory by default as well?
Not going to happen. I personally _hate_ having to track down author
information and make an authors file, and I suspect many others feel the
same. I've never used this feature in git-svn on any real repository.
--
Eric Wong
next prev parent reply other threads:[~2007-11-17 20:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 14:28 BUG: git-svn does not escape literal backslashes in author names Adrian Wilkins
2007-11-17 20:18 ` BUG in gitk (was: Re: BUG: git-svn does not escape literal backslashes in author names.) Benoit Sigoure
2007-11-17 20:43 ` Eric Wong [this message]
2007-11-17 23:17 ` BUG: git-svn does not escape literal backslashes in author names Andreas Ericsson
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=20071117204348.GA16333@muzzle \
--to=normalperson@yhbt.net \
--cc=adrian.wilkins@gmail.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 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.