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

Re: --first-parent plus path limiting

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 29, 2008, 09:11 UTC
Message-ID
<7v63xdov20.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<479EEC3D.9030100@viscovery.net>
Johannes Sixt <j.sixt@viscovery.net> writes:
> I was expecting that it works like "First follow the first-parent, and
> then simplify the history with respect to builtin-fetch.c."

If you first follow the first-parent, the result will by definition not have any merges, so there is nothing left to simplify. History simplification is about merge removal, looking at all parents.

Removing commits from a single strand of pearls that do not touch the specified pathspecs is called "--dense" (which is on the default) and can be disabled with "--sparse".

So, no, it is not a matter of definition, as "first follow the first-parent then simplify" does not make much sense.

Previous: Johannes SixtNext: Johannes Sixt
Message 4 of 6 in “--first-parent plus path limiting”
  1. Johannes SixtJan 29, 2008
  2. Junio C HamanoJan 29, 2008
  3. Johannes SixtJan 29, 2008
  4. Junio C HamanoJan 29, 2008
  5. Johannes SixtJan 29, 2008
  6. Junio C HamanoJan 29, 2008

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.