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

Re: Assessing about commit order in upstream Linux

From
Junio C Hamano <gitster@pobox.com>
Date
May 26, 2020, 15:21 UTC
Message-ID
<xmqqr1v6oh6y.fsf@gitster.c.googlers.com>
In-Reply-To
<20200526065320.GA18107@lxhi-065.adit-jv.com>
Eugeniu Rosca <erosca@de.adit-jv.com> writes:
> So, the two approaches lead to different results. If you see any false
> assumption or mistaken belief, could you please pinpoint that? TIA.

Perhaps the assumption/belief that the set of commits in a history can be totally ordered is the issue? When multiple people work together on a project, especially in a project where "pull --no-ff" is not enforced, there can exist only partial order among them?

Previous: Eugeniu RoscaNext: Michal Suchánek
Message 2 of 6 in “Assessing about commit order in upstream Linux”
  1. Eugeniu RoscaMay 26, 2020
  2. Junio C HamanoMay 26, 2020
  3. Michal SuchánekMay 26, 2020
  4. Eugeniu RoscaMay 28, 2020
  5. Michal SuchánekMay 28, 2020
  6. Eugeniu RoscaMay 28, 2020

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.