From: David Kastrup <dak@gnu.org>
To: git@vger.kernel.org
Subject: Re: git-svn: Branching clarifications
Date: Sat, 08 Sep 2007 09:58:53 +0200 [thread overview]
Message-ID: <85ir6lziyq.fsf@lola.goethe.zz> (raw)
In-Reply-To: 20070908074944.GC24166@muzzle
Eric Wong <normalperson@yhbt.net> writes:
> 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
prev parent reply other threads:[~2007-09-08 7:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-07 16:47 git-svn: Branching clarifications Russ Brown
2007-09-08 5:21 ` Eric Wong
2007-09-08 6:57 ` David Kastrup
2007-09-08 7:49 ` Eric Wong
2007-09-08 7:58 ` David Kastrup [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=85ir6lziyq.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).