Re: git-svn: Branching clarifications

From: David Kastrup <dak@gnu.org>
Date: Sep 8, 2007, 07:58 UTC
Message-ID: <85ir6lziyq.fsf@lola.goethe.zz>
In-Reply-To: <20070908074944.GC24166@muzzle>

Eric Wong <normalperson@yhbt.net> writes:

Show 12 quoted lines

> David Kastrup <dak@gnu.org> wrote:
>
>> Please.  git-svn is told how to find the trunk on its command line.
>> Nothing makes sense (short of an _explicit_ wish otherwise for
>> which it might make sense to create a command line option) than to
>> map master to the trunk.
>
> Keep in mind that command-line arguments for trunk, branches and tags
> are _all_ optional to git-svn.
>
> If only trunk or nothing is specified, the current behavior will
> always be correct.

Sure, since Subversion does not distinguish trunk, branches, tags, or even projects from each other: they are just naming conventions in the repository and nothing enforces them. So if you check out a single, named directory, it is natural that this will be master, and tracked.

> There's also a case if only branches and/or tags are specified, with
> no trunk given.  That would need to be handled, somehow...

Just barf unless a --master=thisbranch option is given. If you want to, you can allow multiple --track=remotebranch options as well, giving you a tracking branch for the specified remote branches under their original name.

Something like that.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum