From: "Patrick Doyle" <wpdster@gmail.com>
To: git <git@vger.kernel.org>
Subject: Why does git-svn dcommit rewrite the log messages?
Date: Wed, 1 Aug 2007 17:19:19 -0400 [thread overview]
Message-ID: <e2a1d0aa0708011419m1f6cb323ge9e93680147a298@mail.gmail.com> (raw)
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.
--wpd
next reply other threads:[~2007-08-01 21:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 21:19 Patrick Doyle [this message]
2007-08-02 19:44 ` Why does git-svn dcommit rewrite the log messages? Sam Vilain
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=e2a1d0aa0708011419m1f6cb323ge9e93680147a298@mail.gmail.com \
--to=wpdster@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 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).