From: Nicolas Pitre <nico@cam.org>
To: Jeff King <peff@peff.net>
Cc: Carl Worth <cworth@cworth.org>, Junio C Hamano <junkio@cox.net>,
git@vger.kernel.org
Subject: Re: Difficulties in advertising a new branch to git newbies
Date: Tue, 30 Jan 2007 20:48:13 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0701302042160.3021@xanadu.home> (raw)
In-Reply-To: <20070130231015.GB10075@coredump.intra.peff.net>
On Tue, 30 Jan 2007, Jeff King wrote:
> On Tue, Jan 30, 2007 at 12:13:26PM -0800, Carl Worth wrote:
>
> > Also, if I'm willing to assume (or insist) that users have git 1.5 or
> > newer, it'd be nice to be able to drop the "-b build" thing thanks to
> > the new detached HEAD support. But if I suggest doing just:
> >
> > git checkout origin/proposed-fix
> >
> > the user is presented with the following message which is much more
> > scary than useful in this situation:
> >
> > warning: you are not on ANY branch anymore.
> > If you meant to create a new branch from the commit, you need -b to
> > associate a new branch with the wanted checkout. Example:
> > git checkout -b <new_branch_name> origin/proposed-fix
Note that the latest revision on the master branch of git has a slightly
less scary message.
> I don't see any reason why we can't scare the user when making a commit,
> instead of just checkout out to look around. Something like the patch
> below. It needs a few things:
> - remove the old checkout message
I don't think that is a good idea in general.
It is already kind of a challenge to teach people about git's branch
concept. The detached head is yet another exotic thing about git that
is sure not to be really obvious to everyone. Now if you remove the
message to hide the detached head state from the user just to come later
on with a "hey btw did you know that your head was detached?" message
then you can be assured that most people will simply go WTF.
Nicolas
next prev parent reply other threads:[~2007-01-31 1:48 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-30 20:13 Difficulties in advertising a new branch to git newbies Carl Worth
2007-01-30 21:02 ` Jakub Narebski
2007-01-30 21:25 ` Yann Dirson
2007-01-30 21:31 ` Jakub Narebski
2007-01-30 21:32 ` Junio C Hamano
2007-01-30 21:40 ` Jakub Narebski
2007-01-30 22:33 ` Matthias Lederhofer
2007-01-30 22:36 ` Matthias Lederhofer
2007-01-30 23:10 ` Jeff King
2007-01-31 1:34 ` Junio C Hamano
2007-01-31 1:51 ` Nicolas Pitre
2007-01-31 3:22 ` Jeff King
2007-01-31 14:59 ` Nicolas Pitre
2007-01-31 17:07 ` Jeff King
2007-01-31 18:59 ` Nicolas Pitre
2007-01-31 22:53 ` Jeff King
2007-01-31 20:20 ` Junio C Hamano
2007-01-31 22:51 ` Theodore Tso
2007-01-31 23:03 ` Junio C Hamano
2007-01-31 23:18 ` Jakub Narebski
2007-01-31 1:48 ` Nicolas Pitre [this message]
2007-01-31 0:10 ` Daniel Barkalow
2007-01-31 1:55 ` Nicolas Pitre
2007-01-31 5:09 ` Daniel Barkalow
2007-01-31 14:31 ` Nicolas Pitre
2007-01-31 14:38 ` J. Bruce Fields
2007-01-31 14:53 ` Jakub Narebski
2007-01-31 15:15 ` Nicolas Pitre
2007-01-31 16:25 ` Daniel Barkalow
2007-01-31 18:25 ` Nicolas Pitre
2007-01-31 13:13 ` Guilhem Bonnefille
2007-01-31 16:06 ` Carl Worth
2007-01-31 16:15 ` Johannes Schindelin
2007-01-31 19:27 ` Santi Béjar
2007-01-31 19:50 ` Carl Worth
2007-02-01 0:20 ` Josef Weidendorfer
2007-02-01 9:02 ` Santi Béjar
2007-02-01 4:12 ` Jakub Narebski
2007-02-06 5:51 ` Carl Worth
2007-02-06 6:37 ` Junio C Hamano
2007-02-06 7:25 ` Junio C Hamano
2007-02-06 7:31 ` Jeff King
2007-02-06 18:53 ` Carl Worth
2007-02-06 19:14 ` Junio C Hamano
2007-02-06 19:39 ` Carl Worth
2007-02-06 19:58 ` Jakub Narebski
2007-02-06 7:28 ` Jeff King
2007-02-06 7:46 ` Junio C Hamano
2007-02-06 8:12 ` Jeff King
2007-02-06 15:33 ` Nicolas Pitre
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0701302042160.3021@xanadu.home \
--to=nico@cam.org \
--cc=cworth@cworth.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=peff@peff.net \
/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.
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 NNTP newsgroup(s).