From: Avi Kivity <avi@qumranet.com>
Date: Mon, 24 Dec 2007 08:36:37 GMT
Subject: Re: [PATCH] Document git rev-list --first-parent
Message-ID: <476F6F95.1030506@qumranet.com>
In-Reply-To: <7v3atstry4.fsf@gitster.siamese.dyndns.org>

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; I can describe my own:

I have a post-receive hook which sends all patches since the last push.  
To avoid sending the constituent commits of a pull, I use --first-parent 
to throw away anything I did not commit directly.

[Initially I used ^origin to cancel out these merges, but that failed as 
soon as I merged from some other branch]

I'm not sure this is what you meant.  Let me know, and I will update the 
patch.

-- 
error compiling committee.c: too many arguments to function