From: Johannes Sixt <j.sixt@viscovery.net>
To: Andreas Hartmetz <ahartmetz@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git branch documentation improvements
Date: Fri, 07 May 2010 09:20:15 +0200 [thread overview]
Message-ID: <4BE3BF2F.8050903@viscovery.net> (raw)
In-Reply-To: <201005070024.41172.ahartmetz@gmail.com>
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
next prev parent reply other threads:[~2010-05-07 7:20 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 [this message]
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=4BE3BF2F.8050903@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=ahartmetz@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 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).