From: Junio C Hamano <junkio@cox.net>
Date: Fri, 18 Nov 2005 22:18:14 GMT
Subject: Re: [PATCH rev-list.c] max-count in terms of intersection
Message-ID: <7v1x1dha6x.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <20051118214722.4449.qmail@web31813.mail.mud.yahoo.com>

Luben Tuikov <ltuikov@yahoo.com> writes:

> diff-tree 768b79de9eadc38a839332df0fcce021f7174d6d (from 2e67a5f449f4026097494569f871d79bf263ab28)
> tree 6403fc730f8d5843043788f4c2f466727ba94bc0
> parent 2e67a5f449f4026097494569f871d79bf263ab28
> author Luben Tuikov <ltuikov@yahoo.com> 1132349344 -0500
> committer Luben Tuikov <ltuikov@yahoo.com> 1132349344 -0500
>
>     [PATCH rev-list.c] max-count in terms of intersection
>     

Documentation/SubmittingPatches, perhaps?

>     When a path designation is given, max-count counts the number
>     of commits therein (intersection), not globally.

This makes sense, but I wonder if the same logic applies to
max_age as well.  If we have clock-skewed commits that are
skipped by the DENSE processing, we probably do not want them to
be affecting what to do on the commits that matter.