git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Ferris Nicolaisen <tfnico@gmail.com>
To: "John M. Dlugosz" <ngnr63q02@sneakemail.com>
Cc: git@vger.kernel.org
Subject: Re: git-svn and comitter names
Date: Tue, 2 Aug 2011 16:59:36 +0200	[thread overview]
Message-ID: <CAEcj5uWO+ydhQFScCirfQeXnOFPget6O7n6PHygCUm8ytwLFsA@mail.gmail.com> (raw)
In-Reply-To: <6517-1311952613-96947@sneakemail.com>

On Fri, Jul 29, 2011 at 5:16 PM, John M. Dlugosz
<ngnr63q02@sneakemail.com> wrote:
> I just grabbed a repository using git-svn, and the commiter name shows a
> GUID for the domain name.  For example,
>
>    first.last <first.last@5ab5abacd-6ff9-f940-aeea-106a2a325327>
>
> I set my git name and email address to show what I want in the end, the real
> company email address.  Will this apparent mapping be a problem when I
> dcommit?

Hi John,

No, it won't be a problem. This is the default "mapping" in git-svn.

The committer name is only visible in your git-svn clone. When you
dcommit, it will use your normal SVN username, the same one which is
used when you use SVN normally.

Your configured git name and email will be used in your local commits,
but as soon as you dcommit, those commits are rewritten to use this
username@uuid style.

If you think this is really annoying, or you are planning to make a
permanent migration away from SVN, you can use an authors-file when
doing the initial git-svn clone. See
http://www.kernel.org/pub/software/scm/git/docs/git-svn.html for more
info on the --authors-file option.

      reply	other threads:[~2011-08-02 14:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-29 15:16 git-svn and comitter names John M. Dlugosz
2011-08-02 14:59 ` Thomas Ferris Nicolaisen [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=CAEcj5uWO+ydhQFScCirfQeXnOFPget6O7n6PHygCUm8ytwLFsA@mail.gmail.com \
    --to=tfnico@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=ngnr63q02@sneakemail.com \
    /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).