All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Martin Nordholts <enselic@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Clarify the git-branch documentation of default start-point
Date: Wed, 17 Jun 2009 22:48:49 -0700	[thread overview]
Message-ID: <7vprd2148u.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1245303673.24201.3.camel@localhost.localdomain> (Martin Nordholts's message of "Thu\, 18 Jun 2009 07\:41\:13 +0200")

Martin Nordholts <enselic@gmail.com> writes:

> -	is omitted, the current branch is assumed.
> +	is omitted, the current branch is assumed.  Note that checking
> +	out a remote branch does not make it the current branch.  If a
> +	remote branch is desired as start-point it must be an explicity
> +	specified.

The first new sentence says

	$ git checkout origin/next

does not mean you will be _on_ the remote branch, 'next' you got from me
in this example.  By definition you cannot be on anything but a local
branch, so the sentence is correct.

But "it" in the second new sentence is unclear.

You probably wanted to answer "If I wanted to have _my own 'next' branch_
that tracks 'next' from the remote, what should I do?"

And the answer would be either

	$ git checkout -t -b next origin/next

or its shorthand invented by Dscho which is

	$ git checkout -t origin/next

Now, is "it must be (an) explicit(l)y specified" a correct instruction to
lead the readers to these solutions?

  reply	other threads:[~2009-06-18  5:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-18  5:41 [PATCH] Clarify the git-branch documentation of default start-point Martin Nordholts
2009-06-18  5:48 ` Junio C Hamano [this message]
2009-06-18  6:04   ` Martin Nordholts
2009-06-18  7:33     ` Junio C Hamano
2009-06-18 17:21       ` Martin Nordholts
2009-06-18  7:57     ` Michael J Gruber

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=7vprd2148u.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=enselic@gmail.com \
    --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.
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.