From: "Björn Steinbrink" <B.Steinbrink@gmx.de>
To: Benoit SIGOURE <tsuna@lrde.epita.fr>
Cc: git@vger.kernel.org
Subject: Re: git-svn merge helper
Date: Mon, 1 Oct 2007 04:50:59 +0200 [thread overview]
Message-ID: <20071001025059.GA29323@atjola.homenet> (raw)
In-Reply-To: <1EF130A4-3CC7-4A42-9166-3539D9A38828@lrde.epita.fr>
On 2007.09.30 16:15:49 +0200, Benoit SIGOURE wrote:
> On Sep 30, 2007, at 1:05 PM, Björn Steinbrink wrote:
>
>> Hi,
>>
>> I recently discovered git-svn and absolutey love it. One thing that I'm
>> missing though, is an equivalent of "svn merge" for merging between svn
>> remotes, to support the SVN way of using "squashed" merges, where you
>> just note the merge meta-data in the commit message. "git merge" didn't
>> work for me (and probably isn't expected to work) to merge between two
>> svn branches, so I've resorted to cherry-picking the required commits
>> one by one into a temporary branch and then squashing them together by
>> doing a --squash merge with a second temporary branch (as in [1]).
>
> I fail to see why you'd want to reproduce the broken behavior of svn merge.
> Anyways, git-svn is a great way to merge SVN branches, unfortunately it
> can't detect when merges happened on the SVN side. I think you can use it
> nevertheless by manually adding a graft at the last merge point, which
> would help you merging the right revisions without having to specify what
> needs to be merged (unless someone made another merge on the SVN side, in
> which case you need to update your graft).
Then how does that work? The manpage explicitly says that I should not
use git-{pull,merge} on branches I want to dcommit from. And a trivial
test immediately got the expected effect of git-svn trying to commit to
trunk instead of the branch.
Thanks,
Björn
next prev parent reply other threads:[~2007-10-01 2:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-30 11:05 git-svn merge helper Björn Steinbrink
2007-09-30 14:15 ` Benoit SIGOURE
2007-10-01 2:50 ` Björn Steinbrink [this message]
2007-10-01 7:56 ` Benoit SIGOURE
[not found] ` <8c5c35580710010113v7d4ad14bt129b7cb12d8f4fb8@mail.gmail.com>
2007-10-02 21:14 ` Björn Steinbrink
2007-10-02 22:04 ` Steven Walter
2007-10-02 22:38 ` Björn Steinbrink
2007-10-03 0:42 ` Steven Walter
2007-10-03 1:02 ` Björn Steinbrink
2007-10-03 11:40 ` Andreas Ericsson
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=20071001025059.GA29323@atjola.homenet \
--to=b.steinbrink@gmx.de \
--cc=git@vger.kernel.org \
--cc=tsuna@lrde.epita.fr \
/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).