From: Sergei Organov <osv@javad.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] user-manual.txt: fix a few mistakes
Date: Fri, 16 Nov 2007 14:34:22 +0300 [thread overview]
Message-ID: <87sl361l1d.fsf@osv.gnss.ru> (raw)
In-Reply-To: <20071116035416.GF18909@fieldses.org> (J. Bruce Fields's message of "Thu\, 15 Nov 2007 22\:54\:16 -0500")
"J. Bruce Fields" <bfields@fieldses.org> writes:
> On Thu, Nov 15, 2007 at 01:36:40PM +0300, Sergei Organov wrote:
>> "J. Bruce Fields" <bfields@fieldses.org> writes:
[...]
>> >> @@ -1567,8 +1567,8 @@ old history using, for example,
>> >> $ git log master@{1}
>> >> -------------------------------------------------
>> >>
>> >> -This lists the commits reachable from the previous version of the head.
>> >> -This syntax can be used to with any git command that accepts a commit,
>> >
>> > I actually prefer "head" here. On something like:
>> >
>> > A--B--C
>> > /
>> > o--o--o
>> > \
>> > o--o--o
>> >
>> >
>> > The term "branch" could be used to refer to the whole line of
>> > development consisting of A, B, and C. The term "head", on the other
>> > hand, refers to either C or a ref that points to it. We also use the
>> > terms "branch head" or just "branch" for that case, but I think "head"
>> > is more precise.
>>
>> Then I'd suggest to be precise here, e.g.:
>>
>> "This lists the commits reachable from the previous version of the
>> "master" branch head."
>
> That sounds sensible to me, sure.
OK, I've just submitted patch for that.
--
Sergei.
prev parent reply other threads:[~2007-11-16 11:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 18:19 [PATCH] user-manual.txt: fix a few mistakes Sergei Organov
2007-11-14 7:19 ` Junio C Hamano
2007-11-14 12:46 ` Sergei Organov
2007-11-14 18:13 ` J. Bruce Fields
2007-11-14 18:18 ` J. Bruce Fields
2007-11-14 19:42 ` Junio C Hamano
2007-11-14 19:44 ` J. Bruce Fields
2007-11-15 10:36 ` Sergei Organov
2007-11-16 3:54 ` J. Bruce Fields
2007-11-16 11:34 ` Sergei Organov [this message]
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=87sl361l1d.fsf@osv.gnss.ru \
--to=osv@javad.com \
--cc=bfields@fieldses.org \
--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 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.