On Tue, Mar 22, 2011 at 1:36 PM, Thomas Ferris Nicolaisen
>> 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).
> How about having people..
> * cloning the bare repository (so they don't have to wait for the very
> long git svn clone process)
> * doing a git svn init -s svn_url (like it is configured in the fetching repo)
> * dcommit to svn themselves with "upci".
>> I would also have to set up automatic scripts to dcommit when everyone
>> commits as well.
> I think it's best that people themselves are responsible for running
> dcommit/upci. Automating committing to svn like this can be a bit
I don't quite follow what you mean here.
git svn init -s svn_url svn_dir
just sets up an empty situation. To get the "bare" repository,
wouldn't I have to have the git svn be fully cloned?
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 firstname.lastname@example.org.
To unsubscribe from this group, send email to
For more options, visit this group at