git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Hudec <bulb@ucw.cz>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Automating svn<->git gateway
Date: Wed, 13 Oct 2010 19:17:34 +0200	[thread overview]
Message-ID: <20101013171734.GA3693@efreet.light.src> (raw)
In-Reply-To: <201010130125.49725.jnareb@gmail.com>

On Wed, Oct 13, 2010 at 01:25:48 +0200, Jakub Narebski wrote:
> On wtorek 12. października 2010 22:31, Jan Hudec napisał:
> > So while I'm sure the native SVN support will solve the quirks and bugs of
> > git-svn, it will not do away with need for the gateway repository that will
> > somehow synchronize itself with subversion.
> 
> Well, I think that native SVN support would allow to treat subversion
> repository as one of repositories in the network of repositories.  Those
> repositories could be set in that pushing to central git repository pushes
> also to subversion repository, and like central git repository fetches
> from leaf repositories, it would fetch from subversion repository.

Yes. Except I don't know how to do the "pushing to central git repository
pushes also to..." part. Subversion or not.

Though, I guess if it worked well enough to preserve the merge commit (i.e.
when I push and pull, I see the commit I pushed, not any kind of rewrite),
pushing in update-hook would be quite many bits simpler.

-- 
						 Jan 'Bulb' Hudec <bulb@ucw.cz>

  reply	other threads:[~2010-10-13 17:17 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
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 [this message]
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=20101013171734.GA3693@efreet.light.src \
    --to=bulb@ucw.cz \
    --cc=git@vger.kernel.org \
    --cc=jnareb@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).