On Tue, Mar 22, 2011 at 1:25 PM, Thomas Ferris Nicolaisen
<tfn...@gmail.com> wrote:
> Just to be clear, the upci alias is explained 
> here: http://blog.tfnico.com/2010/11/git-svn-mirror-for-multiple-branches.html
> It's defined as:
> upci = !git update-ref refs/remotes/$(git branch | grep '^*' | awk '{print 
> $2}') refs/remotes/origin/$(git branch|grep '^*'|awk '{print $2}') && git svn 
> dcommit
> The above does update-ref and dcommit on the current branch.
> If you want to dcommit on another branch, you have to check it out first:
> > git upci
> > git co b_another_branch
> > git commit changes
> > git upci
> If I understand you correctly, you want to automatically do an "upci" with 
> each change in each branch.
> I don't know how to achieve this. git svn uses the work-dir to operate, so I 
> think you have to have the branch you want to dcommit actually checked out.
> Perhaps a possible workaround would be to have a fetching repository for each 
> branch you wish to keep in sync? This obviously doesn't scale well, but for 
> less than a handful branches it could work.

Thanks. Unfortunately I do have a lot of branches. Actually, the fetch
does pick up all branches and sends them to the "bare" repository so
that every fetch updates every branch. So far it is only the dcommit
that is giving the problem. I am trying to avoid having to get
everyone use a git svn clone from the original svn repository rather
than a git clone from a git repository. So far, the only way to do
this is to only dcommit to the trunk (or master).

I would also have to set up automatic scripts to dcommit when everyone
commits as well.

       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 git-users@googlegroups.com.
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to