From: Junio C Hamano <gitster@pobox.com>
To: Avi Kivity <avi@qumranet.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Document git rev-list --first-parent
Date: Mon, 24 Dec 2007 01:13:25 -0800 [thread overview]
Message-ID: <7vprwwsbey.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <476F6F95.1030506@qumranet.com> (Avi Kivity's message of "Mon, 24 Dec 2007 10:36:37 +0200")
Avi Kivity <avi@qumranet.com> writes:
> Junio C Hamano wrote:
>> Avi Kivity <avi@qumranet.com> writes:
>>
>>> Document git rev-list's --first-parent option. Documentation taken from
>>> git log.
>>> ...
>>> +--first-parent::
>>> + Follow only the first parent commit upon seeing a merge
>>> + commit. This option gives a better overview of the
>>> + evolution of a particular branch.
>>> +
>>>
>>
>> I am afraid that this description is not sufficient. The
>> history given by --first-parent is useful only in a very limited
>> use case, and the user needs to be aware of it.
>
> I don't know which use case you are referring to...
Please read the commit log message you snarfed the description
again.
First-parent is useful only if you are the primary integrator
and do not fast-forward from other people. Only in that case,
you will see the overview of "the primary integration branch".
Otherwise you will observe the history viewed by whoever
happened to make a merge, which would switch every time you
cross the fast-forward boundary.
Making it sound as if it always will give a better overview is
misleading.
next prev parent reply other threads:[~2007-12-24 9:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-24 8:20 [PATCH] Document git rev-list --first-parent Avi Kivity
2007-12-24 8:30 ` Junio C Hamano
2007-12-24 8:36 ` Avi Kivity
2007-12-24 9:13 ` Junio C Hamano [this message]
2007-12-24 9:40 ` Avi Kivity
2007-12-24 9:58 ` Junio C Hamano
2007-12-24 10:14 ` Avi Kivity
2007-12-24 16:37 ` Avi Kivity
2007-12-25 9:35 ` Junio C Hamano
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=7vprwwsbey.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=avi@qumranet.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).