From: Andreas Hartmetz <ahartmetz@gmail.com>
To: git@vger.kernel.org
Cc: Jon Seymour <jon.seymour@gmail.com>
Subject: Re: git branch documentation improvements
Date: Fri, 7 May 2010 04:28:16 +0200 [thread overview]
Message-ID: <201005070428.16827.ahartmetz@gmail.com> (raw)
In-Reply-To: <r2l2cfc40321005061559p9d3a5392rdc2b30f63a34ab9b@mail.gmail.com>
On Friday 07 May 2010 00:59:22 Jon Seymour wrote:
> On Fri, May 7, 2010 at 8:24 AM, Andreas Hartmetz <ahartmetz@gmail.com>
wrote:
> > Today I read the git branch documentation and noticed a few things,
> > mostly style and consistency related, that could easily be improved, so
> > I did just that.
> > Please consider merging the attached patch if it looks good, or tell me
> > what you don't like about it.
> > 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.
>
> While I agree with you start start-point is probably the wrong name
> for this parameter, I wonder whether branch-head might be too
> suggestive that the value of that parameter must itself be an existing
> branch head.
>
> I think the term "head-commit" would be a more accurate way to
> describe the possible values of this parameter. That is, it is the
> commit that will become the head of the new branch.
>
Another suggestion I came up with much earlier that I recalled just now:
<new-head>
next prev parent reply other threads:[~2010-05-07 2:28 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 [this message]
2010-05-07 7:20 ` Johannes Sixt
2010-05-07 8:40 ` Jon Seymour
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=201005070428.16827.ahartmetz@gmail.com \
--to=ahartmetz@gmail.com \
--cc=git@vger.kernel.org \
--cc=jon.seymour@gmail.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).