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, 23:42 UTC
Message-ID
<7vfyptfrqj.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20051118224233.50766.qmail@web31805.mail.mud.yahoo.com>
Luben Tuikov <ltuikov@yahoo.com> writes:
Show 9 quoted lines
>> 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.
>
> As far as I understand it, I think max-age is fine the way
> it is.  After all, max-age depends on date/time which is
> absolute (i.e. applies to commits in the whole set and in
> the intersection just the same).

It is recorded absolutely but what if committer's clock is broken on one commit but not others, and if you are not using the default sort_by_date() (e.g. --topo-order)?

Previous: Luben Tuikov
Message 4 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.