# git-svn dcommit always uses my own name

3 messages from 2008-04-15 to 2008-04-15. Participants: Avery Pennarun, Richard Quirk.
Thread: https://gitlist.dev/t/13128

## Avery Pennarun, 2008-04-15 21:25

Subject: git-svn dcommit always uses my own name
Message-ID: <32541b130804151425o6cf7646co541fb7cc85115606@mail.gmail.com>
URL: https://gitlist.dev/e/32541b130804151425o6cf7646co541fb7cc85115606%40mail.gmail.com

```
Hi all,

Here's the workflow I'm using:

- I check out the central svn repository into a shared git repo using git-svn

- Each team member clones the shared repo, works in it, etc.

- I integrate their changes using git-pull, merge, rebase, etc,
forming a linearized history suitable for git-svn

- I run git-svn dcommit.

However, when I do this, all the commits to svn end up having *my*
userid attached, rather than the userid of the git user.  If I do "git
log" before "git-svn dcommit", it shows all the right authors, but
this information is lost when I dcommit.

Is there a way to not lose this information?

Thanks,

Avery

```

## Richard Quirk, 2008-04-15 22:08

Subject: Re: git-svn dcommit always uses my own name
Message-ID: <cac9e4380804151508p688bd7b7o1eb413b4133dad57@mail.gmail.com>
URL: https://gitlist.dev/e/cac9e4380804151508p688bd7b7o1eb413b4133dad57%40mail.gmail.com
In-Reply-To: <32541b130804151425o6cf7646co541fb7cc85115606@mail.gmail.com>

```
On Tue, Apr 15, 2008 at 11:25 PM, Avery Pennarun <apenwarr@gmail.com> wrote:

>  However, when I do this, all the commits to svn end up having *my*
>  userid attached, rather than the userid of the git user.  If I do "git
>  log" before "git-svn dcommit", it shows all the right authors, but
>  this information is lost when I dcommit.
>
>  Is there a way to not lose this information?
>

Subversion only remembers the user that made the commit; there's no
way to tell it that someone else wrote the patch and that you just
committed it. However, examining git-svn, there seems to be an
undocumented option. You can do this:

git svn dcommit --use-log-author

That uses the Signed-off-by: field in the commit message to extract
the author information. Of course it won't rescue the author field on
old commits, and you have to have Signed-off-by on any new ones to
gain any benefit.

regards,
Richard

```

## Avery Pennarun, 2008-04-15 22:35

Subject: Re: git-svn dcommit always uses my own name
Message-ID: <32541b130804151535g56a8133dk863da833be87fb08@mail.gmail.com>
URL: https://gitlist.dev/e/32541b130804151535g56a8133dk863da833be87fb08%40mail.gmail.com
In-Reply-To: <cac9e4380804151508p688bd7b7o1eb413b4133dad57@mail.gmail.com>

```
On 4/15/08, Richard Quirk <richard.quirk@gmail.com> wrote:
> Subversion only remembers the user that made the commit; there's no
>  way to tell it that someone else wrote the patch and that you just
>  committed it. However, examining git-svn, there seems to be an
>  undocumented option. You can do this:
>
>  git svn dcommit --use-log-author
>
>  That uses the Signed-off-by: field in the commit message to extract
>  the author information. Of course it won't rescue the author field on
>  old commits, and you have to have Signed-off-by on any new ones to
>  gain any benefit.

Hmm, it looks like --use-log-author really affects git-svn fetch, not
commit: in other words, it pulls the signed-off-by information from
the svn repo when importing the commits back into git.

This is actually the clue I needed, which I think is: use
signed-off-by lines in the first place, because that will solve my
problem of tracking who wrote each patch :)

Have fun,

Avery

```