From: Jan Hudec <bulb@ucw.cz>
To: Joshua Shrader <jshrader83@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Automating svn<->git gateway
Date: Tue, 12 Oct 2010 19:35:25 +0200 [thread overview]
Message-ID: <20101012173524.GB30870@efreet.light.src> (raw)
In-Reply-To: <AANLkTikp1e72RQs3QQTqyg2m4Vk6rjz=Sv33iHAxDKoP@mail.gmail.com>
On Mon, Oct 11, 2010 at 16:33:47 -0400, Joshua Shrader wrote:
> Check out the article and third-to-last comment (as of today) at
> http://blog.emmanuelbernard.com/2010/05/git-how-my-life-has-improved-since-last-month-when-i-used-svn/comment-page-1/#comment-2248
>
> The comment (by Josh) is mine, and details how I've approached this
> problem. It's worked very well for us, and follows from a workflow
> presented in Jon Loeliger's "Version Control with Git." I haven't
> messed with any hooks, but I'd imagine that wouldn't be too difficult.
> Right now, we keep a couple legacy maintenance SVN branches sync'd up
> with their corresponding Git branches. The one thing that we haven't
> attempted (and don't plan on) is creating a new branch in Git that we
> want to duplicate in SVN. We're only syncing branches that existed in
> SVN prior to our move to Git. Any new branches are "Git-only."
Thanks. That's the workflow I had in mind. I already did something similar
ages ago with GNU arch and CVS, but the exact outline for git-svn will be
definitely helpful. Especially the exact order in which the merges need to be
done.
For my purpose I'll definitely need to automate it, because we often need to
see each other's changes quickly (often somebody needs a fix from somebody
else to be able to test something else or to base other changes on it). So
requiring to log in on the server and run the synchronization manually would
add too much overhead.
> On Mon, Oct 11, 2010 at 3:30 PM, Jan Hudec <bulb@ucw.cz> wrote:
> > Hello Folks,
> >
> > I want to set up a gateway between subversion and git, which would keep the
> > master synchonized with subversion trunk, both ways, and allow working with
> > any additional branches independent of subversion. For users it should behave
> > as any other shared git repository accessed by push and pull. And it needs to
> > be automatic.
> >
> > Did anybody try to set up something like this?
--
Jan 'Bulb' Hudec <bulb@ucw.cz>
next prev parent reply other threads:[~2010-10-12 17:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 19:30 Automating svn<->git gateway Jan Hudec
2010-10-11 20:33 ` Joshua Shrader
2010-10-12 17:35 ` Jan Hudec [this message]
2010-10-12 19:54 ` Jakub Narebski
2010-10-12 20:31 ` Jan Hudec
2010-10-12 23:25 ` Jakub Narebski
2010-10-13 17:17 ` Jan Hudec
2010-10-15 16:48 ` Jakub Narebski
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=20101012173524.GB30870@efreet.light.src \
--to=bulb@ucw.cz \
--cc=git@vger.kernel.org \
--cc=jshrader83@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).