git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Seymour <jon.seymour@gmail.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Andreas Hartmetz <ahartmetz@gmail.com>, git@vger.kernel.org
Subject: Re: git branch documentation improvements
Date: Fri, 7 May 2010 18:40:06 +1000	[thread overview]
Message-ID: <m2t2cfc40321005070140m85d51db7id75b5b897f2acc00@mail.gmail.com> (raw)
In-Reply-To: <4BE3BF2F.8050903@viscovery.net>

My minor quibble with start-point is that the naive user may assume
that, like CVS or SVN, git has some persistent notion of a "start
point".

In reality, git only tracks heads. A term like "head-commit" is, IMO,
more precise than "start-point" and does not potentially convey the
false notion that git knows or cares about the point at which a branch
was "started".

jon.

On Fri, May 7, 2010 at 5:20 PM, Johannes Sixt <j.sixt@viscovery.net> wrote:
> Am 5/7/2010 0:24, schrieb Andreas Hartmetz:
>> The most significant change is renaming <start-point> (or is it
>> <startpoint>...) to <branch-head> because even I as a relative beginner know
>> that a branch is defined by its (movable) head, and <start-point> *does*
>> actually specify the new branch head if I'm not mistaken.
>
> But what is wrong with "start-point"? It precisely conveys the meaning of
> the parameter.
>
> -- Hannes
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

  reply	other threads:[~2010-05-07  8:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-06 22:24 git branch documentation improvements Andreas Hartmetz
2010-05-06 22:59 ` Jon Seymour
2010-05-07  1:04   ` Andreas Hartmetz
2010-05-07  2:28   ` Andreas Hartmetz
2010-05-07  7:20 ` Johannes Sixt
2010-05-07  8:40   ` Jon Seymour [this message]
2010-05-08 16:39   ` Andreas Hartmetz
2010-05-10  6:22     ` Johannes Sixt
2010-05-11 18:27       ` Andreas Hartmetz

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=m2t2cfc40321005070140m85d51db7id75b5b897f2acc00@mail.gmail.com \
    --to=jon.seymour@gmail.com \
    --cc=ahartmetz@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=j.sixt@viscovery.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).