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

Re: Commit graph not using minimal number of columns

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 27, 2023, 18:24 UTC
Message-ID
<xmqq4jp1kwu2.fsf@gitster.g>
In-Reply-To
<7ec7f7b2-3e7a-afb9-7042-a4375970e8d8@github.com>
Derrick Stolee <derrickstolee@github.com> writes:
> Corrected commit date should be equal to commit date unless there
> is clock skew causing a commit to be older than its parent, (or
> we have a path of commits with equal commit date) so I don't
> anticipate that being helpful in general.
Yes, exactly.  For normal cases it should not matter.

I was wondering if the current --date-order shows commits in an order that end-users find unnatural in a branchy history with many commits that have wrong commit dates, and if so, tweaking the date-order to instead use the corrected commit date may help and if so how much.

Thanks.
Previous: Derrick Stolee
Message 8 of 8 in “Commit graph not using minimal number of columns”
  1. Javier MoraApr 25, 2023
  2. Junio C HamanoApr 25, 2023
  3. Derrick StoleeApr 26, 2023
  4. Junio C HamanoApr 26, 2023
  5. Derrick StoleeApr 26, 2023
  6. Junio C HamanoApr 26, 2023
  7. Derrick StoleeApr 27, 2023
  8. Junio C HamanoApr 27, 2023

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.