From: Martin Nordholts <enselic@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Clarify the git-branch documentation of default start-point
Date: Thu, 18 Jun 2009 08:04:21 +0200 [thread overview]
Message-ID: <1245305061.24201.12.camel@localhost.localdomain> (raw)
In-Reply-To: <7vprd2148u.fsf@alter.siamese.dyndns.org>
On Wed, 2009-06-17 at 22:48 -0700, Junio C Hamano wrote:
> 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.
>
> [...] "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?"
What I am trying to clarify is that a remote branch will never be the
default for the start-point argument to git-branch, so if someone wants
a remote branch as start-point, then the branch must be explicitly
specified.
For this, the first sentence might actually be enough. If a remote
branch never is the current branch, and if start-point defaults to the
current branch, then the start-point can never default to a remote
branch.
Should we just stick to the first sentence then perhaps?
/ Martin
next prev parent reply other threads:[~2009-06-18 6:02 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
2009-06-18 6:04 ` Martin Nordholts [this message]
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=1245305061.24201.12.camel@localhost.localdomain \
--to=enselic@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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).