From: Adam Roben <aroben@apple.com>
To: Pedro Melo <melo@simplicidade.org>
Cc: git@vger.kernel.org
Subject: Re: git-svn capabilities
Date: Sun, 09 Dec 2007 00:37:51 -0800 [thread overview]
Message-ID: <475BA95F.7040403@apple.com> (raw)
In-Reply-To: <DB0B4F17-9E06-4C28-933E-FDEF9BAD6539@simplicidade.org>
Pedro Melo wrote:
> Hi,
>
> I've been following along the gcc/git thread with interest and I've
> used Harvey Harrison recipe
>
> http://article.gmane.org/gmane.comp.version-control.git/67253
>
> with success on several svn repos.
>
> One thing that I'm not sure yet if it is possible to do is this:
>
> can I have a single central git repo that tracks the svn repo, allow
> several developers to use clone to copy that repo, and each one of
> them (after proper manual configuration) uses dcommit to push back to
> svn?
>
> All the recipes so far assume that each developer has to go through
> the initial git-svn fetch and have a copy of the entire SVN repo, and
> that seems wasteful to me.
The "Basic Examples" section of the git-svn man page describe how to do
just that (though only for a single branch).
-Adam
next prev parent reply other threads:[~2007-12-09 8:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-09 8:20 git-svn capabilities Pedro Melo
2007-12-09 8:37 ` Adam Roben [this message]
2007-12-09 11:20 ` Pedro Melo
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=475BA95F.7040403@apple.com \
--to=aroben@apple.com \
--cc=git@vger.kernel.org \
--cc=melo@simplicidade.org \
/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).