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

Re: History over-simplification

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 27, 2007, 05:34 UTC
Message-ID
<7v4phgzn6i.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20070927045640.31040.qmail@science.horizon.com>
linux@horizon.com writes:
Show 13 quoted lines
> These seem like roundabout ways of expressing the requirement.
> The desired rule is "no silent changes in the simplified history".
> E.g. if the revision history of a particular file is:
>
>       +-C-+
>      /     \
> A---B       B---D
>      \     /
>       +-B-+
>
> Then the normal code will notice that there are no changes on the
> lower branch, prune the merge entirely, and simplify to A---B---C---D.
> This is, however, misleading; the true history is A---B---C---B---D.

Do you denote the same content with the same letter in the above?

If so, wouldn't the simplified history be just A-B-D?
Previous: linux@horizon.com
Message 2 of 2 in “Re: History over-simplification”
  1. linux@horizon.comSep 27, 2007
  2. Junio C HamanoSep 27, 2007

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.