From: David Kastrup <dak@gnu.org>
To: Eric Wong <normalperson@yhbt.net>
Cc: Russ Brown <pickscrape@gmail.com>, git@vger.kernel.org
Subject: Re: git-svn: Branching clarifications
Date: Sat, 08 Sep 2007 08:57:27 +0200 [thread overview]
Message-ID: <85r6l9zlt4.fsf@lola.goethe.zz> (raw)
In-Reply-To: <20070908052126.GB28855@soma> (Eric Wong's message of "Fri\, 7 Sep 2007 22\:21\:26 -0700")
Eric Wong <normalperson@yhbt.net> writes:
> git-svn sets "master" to the most recently committed-to branch
> in SVN the first time it fetches. "git-log master" will tell
> you (look at the git-svn-id: lines).
Sigh. Another "surprise the user by an arbitrary looking choice that
might possibly correspond to what he wants done because it something
obscure in the commit history suggests so" design decision.
I don't want my master set according to something that a coworker (or
even myself) happened to commit last to.
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.
As a design rule: don't second-guess the user, _ever_, and
particularly not on decisions with large consequences. A tool should
not have a mind of its own but do what it is told. And if it can't
figure out what it is told, by simple, user-understandable criteria,
barf. And of course have a way to _direct_ it when it can't figure it
out on its own, or if the simple and obvious default would not do the
right thing.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2007-09-08 6:57 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 [this message]
2007-09-08 7:49 ` Eric Wong
2007-09-08 7:58 ` David Kastrup
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=85r6l9zlt4.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
--cc=pickscrape@gmail.com \
/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).