All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jay Soffian <jaysoffian@gmail.com>
Cc: git@vger.kernel.org, Nicolas Pitre <nico@fluxnic.net>
Subject: Re: [PATCH] git-checkout.txt: improve detached HEAD documentation
Date: Mon, 21 Feb 2011 21:56:15 -0800	[thread overview]
Message-ID: <7vd3mkfw8w.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1298179310-46207-1-git-send-email-jaysoffian@gmail.com> (Jay Soffian's message of "Sun\, 20 Feb 2011 00\:21\:50 -0500")

Jay Soffian <jaysoffian@gmail.com> writes:

> +It is sometimes useful to be able to checkout a commit that is not at
> +the tip of any named branch, or even to create a new commit that is not
> +referenced by a named branch. Let's look at what happens when we
> +checkout commit 'b' (here we show three ways this may be done):
>  
> +------------
> +$ git checkout v2.0  # or
> +$ git checkout b     # or
> +$ git checkout master^^

I'd drop the second one, as "b" is not something the end user would type
from the command line (you could say "b's commit ID" but the string 'b' is
not it, unless it is a tag or something, in which case the first one that
uses 'v2.0' already illustrates it), and adjust "three" accordingly.

Other than that, I think this version is a vast improvement over what we
have.

Thanks.

  reply	other threads:[~2011-02-22  5:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-17 19:46 [PATCH] git-checkout.txt: improve detached HEAD documentation Jay Soffian
2011-02-17 19:48 ` Jay Soffian
2011-02-17 20:47 ` Nicolas Pitre
2011-02-17 21:49 ` Junio C Hamano
2011-02-18  0:14   ` Nicolas Pitre
2011-02-18  0:25     ` Junio C Hamano
2011-02-20  5:21   ` Jay Soffian
2011-02-22  5:56     ` Junio C Hamano [this message]
2011-02-22 15:19       ` Jay Soffian

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=7vd3mkfw8w.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jaysoffian@gmail.com \
    --cc=nico@fluxnic.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.