From: Avery Pennarun <apenwarr@gmail.com>
To: Josef Wolf <jw@raven.inka.de>,
Avery Pennarun <apenwarr@gmail.com>,
git@vger.kernel.org
Subject: Re: Trying to sync two svn repositories with git-svn (repost)
Date: Mon, 4 May 2009 11:58:20 -0400 [thread overview]
Message-ID: <32541b130905040858v2a0b7a6br5b056a365fcb6855@mail.gmail.com> (raw)
In-Reply-To: <20090502215852.GJ15420@raven.wolf.lan>
On Sat, May 2, 2009 at 5:58 PM, Josef Wolf <jw@raven.inka.de> wrote:
> Somehow, I still can't get it work. This is what I do:
[...]
> # move stuff from svn-2 to svn-1
> #
> git svn fetch svn-2
> git checkout svn-1
> git cherry-pick 05b964
> [ continue cherry-picking ]
> git merge --no-ff -s ours svn-1
Note that you probably should be merging '-s ours svn-2' here, not
svn-1. svn-1 already contains svn-1 (of course) so that merge didn't
do anything. It most especially doesn't mark svn-1 as being
up-to-date with svn-2, and that's probably going to make trouble
later.
> # check what I have done
> #
> git diff svn-1-orig svn-1/trunk # shows what I expect
This is unsurprising, since you haven't changed either branch during the above.
> # move the result to svn-1
> #
> git checkout svn-1/trunk
> git merge --no-ff svn-1
> git svn dcommit
This looks ok.
> # move stuff from svn-1 to svn-2
> #
> git svn fetch svn-1
> git checkout svn-2
> git cherry-pick -n c9dae
> [ continue cherry-picking ]
> git merge --no-ff -s ours svn-2
Again, you seem to have merged in the wrong branch here. This one
should be svn-1.
> # check what I have done
> #
> git diff svn-2-orig svn-2/trunk # shows what I expect
Again, these branches haven't changed, so no surprise here either.
> # move the result to svn-2
> #
> git checkout svn-2/trunk
> git merge --no-ff svn-2
> git svn dcommit
This seems ok.
> At this point, we should be synchronized.
Yes, although there are no merges between svn-1 and svn-2, so the next
attempt at merging will merge *everything*, causing conflicts.
> git checkout svn-2/trunk
> git svn fetch svn-1
> git merge --no-ff svn-1
>
> BOOM. Although no new commits were fetched, we get a lot of conflicts
> here. So git is not fully aware about the fact that we are synchronized.
You seem to almost have it. Fix the -s ours merges above and I think
you'll be in business.
Have fun,
Avery
next prev parent reply other threads:[~2009-05-04 15:58 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 20:12 Trying to sync two svn repositories with git-svn (repost) Josef Wolf
2009-04-28 20:30 ` Josef Wolf
2009-04-28 20:53 ` Avery Pennarun
2009-04-28 22:37 ` Josef Wolf
2009-04-29 3:19 ` Avery Pennarun
2009-04-29 16:01 ` Josef Wolf
2009-04-29 18:13 ` Avery Pennarun
2009-04-29 22:37 ` Josef Wolf
2009-04-30 2:07 ` Avery Pennarun
2009-04-30 22:28 ` Josef Wolf
2009-04-30 22:59 ` Avery Pennarun
2009-05-01 14:28 ` Josef Wolf
2009-05-01 19:17 ` Avery Pennarun
2009-05-02 21:58 ` Josef Wolf
2009-05-04 15:58 ` Avery Pennarun [this message]
2009-05-04 21:14 ` Josef Wolf
2009-05-06 18:52 ` Josef Wolf
2009-05-06 19:23 ` Avery Pennarun
2009-05-06 22:50 ` Josef Wolf
2009-05-08 20:44 ` Avery Pennarun
2009-05-08 23:58 ` Josef Wolf
2009-05-13 12:09 ` Josef Wolf
2009-05-13 17:28 ` Avery Pennarun
2009-05-13 22:22 ` Josef Wolf
2009-05-14 6:35 ` Avery Pennarun
2009-05-14 21:41 ` Josef Wolf
2009-05-14 21:57 ` Avery Pennarun
2009-05-15 17:52 ` Josef Wolf
2009-05-15 19:05 ` Avery Pennarun
2009-05-17 11:24 ` Josef Wolf
2009-05-20 16:40 ` Josef Wolf
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=32541b130905040858v2a0b7a6br5b056a365fcb6855@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=jw@raven.inka.de \
/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).