On Wed, Mar 23, 2011 at 4:41 PM, Hillel (Sabba) Markowitz
> On Wed, Mar 23, 2011 at 2:03 AM, Thomas Ferris Nicolaisen
> <tfn...@gmail.com> wrote:
>> Almost, this is how:
>> git clone bare-url gitdir
>> cd gitdir
>> git svn init svn-url
>> This is "5. Set up an SVN remote in the developer's repo" in this guide:
> When I do the full git svn clone, it creates the SHA1 files <branch
> name> in .git/refs/remotes. I need to set up a loop to so that it can
> obtain and do the update-ref command. Once I do that, then when I do
> "git svn rebase --all" it actually builds the entire same way as if I
> had built it from the start. Is there a good way of doing this?
> I am trying to set it up with a python script so that the other
> developers in the team can do this quickly.
I assume now, that you are trying to do a setup equal to the one I've
written about in my blog-post. If not, I've misunderstood (and my
instructions will be misleading, most likely).
The idea in said blog-post is that the developers won't have to do git
svn rebase --all.
They can just do pull --rebase from the bare repository, which is
automatically synced with svn by the fetching repository.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To post to this group, send email to email@example.com.
To unsubscribe from this group, send email to
For more options, visit this group at