From: Michael J Gruber <git@drmicha.warpmail.net>
To: Josef Wolf <jw@raven.inka.de>, git@vger.kernel.org
Subject: Re: How to sync two svn repositories via git?
Date: Thu, 02 Apr 2009 09:41:31 +0200 [thread overview]
Message-ID: <49D46C2B.3080100@drmicha.warpmail.net> (raw)
In-Reply-To: <20090401223052.GA28619@raven.wolf.lan>
Josef Wolf venit, vidit, dixit 02.04.2009 00:30:
> Hello,
>
> I have two subversion repositories which I would like to synchronize via
> git-svn. For this, I have set up a git repository and configured two
> branches to track the subversion repositories via git-svn:
>
> mkdir test-sync
> cd test-sync
> git svn init --stdlayout file://$REPOSDIR/svn-first
>
> for repos in svn-first svn-second; do
> git config svn-remote.$repos.url file://$REPOSDIR/$repos
> git config svn-remote.$repos.fetch trunk:refs/remotes/$repos/trunk
> git config svn-remote.$repos.branches branches/*:refs/remotes/$repos/*
> git config svn-remote.$repos.tags tags/*:refs/remotes/$repos/tags/*
> git svn fetch -R $repos
> git checkout -b $repos $repos/trunk
> done
> git gc
>
> This gives me two remote and two local branches:
>
> master
> svn-first
> * svn-second
> svn-first/trunk
> svn-second/trunk
>
> The first step I'd like to do is to "mirror" the manual merges that were
> done between the subversion repositories in the past:
>
> git checkout svn-first
> git merge -s ours --log commit-of-the-first-merge-in-svn-second
>
> git checkout svn-second
> git merge -s ours --log commit-of-the-first-merge-in-svn-first
>
> This seems to work, but git-gui shows conflicts. How can I get conflicts
> when I use the "-s ours" merge strategy?
What do git status and git diff (--stat, --combined) say?
next prev parent reply other threads:[~2009-04-02 7:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 22:30 How to sync two svn repositories via git? Josef Wolf
2009-04-02 7:41 ` Michael J Gruber [this message]
2009-04-02 10:36 ` 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=49D46C2B.3080100@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--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).