git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH rev-list.c] max-count in terms of intersection

From
Junio C Hamano <junkio@cox.net>
Date
Nov 18, 2005, 22:18 UTC
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:
Show 8 quoted lines
> 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.

Previous: Luben TuikovNext: Luben Tuikov
Message 2 of 4 in “max-count in terms of intersection”
  1. max-count in terms of intersectionLuben Tuikov, Nov 18, 2005
  2. Junio C HamanoNov 18, 2005
  3. Luben TuikovNov 18, 2005
  4. Junio C HamanoNov 18, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.