On Mar 30, 1:43 pm, Thomas Ferris Nicolaisen <tfn...@gmail.com> wrote:
> You are right with one clarification: The svn repository must be set up to
> trigger a rebase in the fetching repository upon committing.
> I've found the best way to do this is to have a svn post-commit hook that
> triggers a job that does this (git svn rebase/fetch + push to bare repo). It
> is also good if this job does some kind of mail notification, so that you
> can see what happens. Personally, I use a Jenkins/Hudson job for this.
> So to be clear: In order to a dcommit - you must have the latest SVN
> revision in your local repository.
> (Normal git-svn users usually achieve this by doing git svn rebase before
> they do git svn dcommit - but with this git-svn-mirror setup, we have to get
> the latest commit through the fetching+bare repo.)
I finally set up a git svn repo in my local area, with the full
complications that needed to be set up and just created a tar file to
be saved in the central repo. Any developer who wants to use git will
get it and untar it in his local area. He will then issue "git svn
rebase --all" to bring it up to date. As a result, the full time
wasting build only had to be done once. THey will then be able to do
the rebase and dcommit whenever they need to. I understand that the
group in charge of maintaining the corporate wide svn repository are
now looking into setting up a git hub and doing a full conversion in
the future. We will see (:-).
Thanks for all your help and your patience in explaining things to me.
Sabba - סבא הלל - Hillel
Hillel (Sabba) Markowitz | Said the fox to the fish, "Join me ashore"
sabbahil...@gmail.com | The fish are the Jews, Torah is our water
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