From: Sam Vilain <sam@vilain.net>
To: Patrick Doyle <wpdster@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: Why does git-svn dcommit rewrite the log messages?
Date: Thu, 02 Aug 2007 12:44:21 -0700 [thread overview]
Message-ID: <46B23415.8030008@vilain.net> (raw)
In-Reply-To: <e2a1d0aa0708011419m1f6cb323ge9e93680147a298@mail.gmail.com>
Patrick Doyle wrote:
> I see that it appends text to the log messages with the SVN repository
> revision and ID. Does it do that because:
>
> 1) That's the _only_ way to keep git & svn in sync
> If so, then I guess I'm out of luck. But it seems (to my
> inexperienced eye) to make branching impossible in git -- as soon as I
> do a "git-svn dcommit", I lose the commit on which my branch was
> originally based. Or, am I missing something?
>
> 2) That was the simplest way to keep them in sync at the time git-svn
> was written and it hasn't bothered anybody enough to go back and fix
> it.
> If so, I'd be glad to see what I could do to fix it. I would also
> appreciate any pointers folks might care to give to get me started.
>
Primarily it's so that the person who pushed via dcommit and people who
sync via git-svn fetch get the same commit ID (assuming they are both
using the same authors map).
It might be possible to store the extra information needed to recreate
exactly the original git commit in SVN revision properties, but this
would need to be implemented once and basically not changed after that.
You can disable this behaviour, but you'll end up with duplicate commits.
Sam.
next prev parent reply other threads:[~2007-08-02 22:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 21:19 Why does git-svn dcommit rewrite the log messages? Patrick Doyle
2007-08-02 19:44 ` Sam Vilain [this message]
2007-08-03 1:44 ` Patrick Doyle
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=46B23415.8030008@vilain.net \
--to=sam@vilain.net \
--cc=git@vger.kernel.org \
--cc=wpdster@gmail.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).