From: Peter Baumann <waste.manager@gmx.de>
To: Richard MUSIL <richard.musil@st.com>
Cc: git@vger.kernel.org
Subject: Re: git-svn: commit author x commit committer issue
Date: Wed, 8 Aug 2007 19:13:23 +0200 [thread overview]
Message-ID: <20070808171323.GD27703@xp.machine.xx> (raw)
In-Reply-To: <46B9C92B.3000000@st.com>
On Wed, Aug 08, 2007 at 03:46:19PM +0200, Richard MUSIL wrote:
> Normally, when patch is applied, git distinguishes commit author and
> commit committer (relying on info from patch).
> However, after the patches are committed to svn repository using:
> git-svn dcommit
> author and committer data are set to same values (or at least time and
> date, I cannot verify it for names).
> I wonder if there is any reason for this behavior, because I would
> definitely like to keep original commit info (which came from patch) in
> my git repository.
I think it is because in SVN, you can't differentiate between author and
committer. And git-svn just commits every local commit to svn, and after
that, it throws away your local commits and uses the info from the
reimported svn commits to recreate those thrown away commits. Thats why
you loose your author name and also your commit date.
Ok, this was a little too simplified, but describes roughly what happens
if you dcommit your changes.
-Peter
next prev parent reply other threads:[~2007-08-08 17:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 13:46 git-svn: commit author x commit committer issue Richard MUSIL
2007-08-08 15:42 ` Quy Tonthat
2007-08-08 17:13 ` Peter Baumann [this message]
2007-08-09 9:45 ` Richard MUSIL
2007-08-16 9:20 ` Eric Wong
2007-08-16 12:13 ` Richard MUSIL
2007-08-17 7:58 ` Eric Wong
2007-08-22 10:07 ` Guilhem Bonnefille
2007-08-22 10:17 ` Guilhem Bonnefille
2007-08-22 21:34 ` Junio C Hamano
2007-08-23 5:05 ` Eric Wong
2007-08-23 8:51 ` Richard MUSIL
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=20070808171323.GD27703@xp.machine.xx \
--to=waste.manager@gmx.de \
--cc=git@vger.kernel.org \
--cc=richard.musil@st.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).