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

Re: git-log on a file, and merges

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 2, 2019, 19:32 UTC
Message-ID
<xmqqtvazjrcj.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<CAA01CspHCKA3itmTxFO1NeNB6DpdFx3CTbXKtO=TvtznLn_zAg@mail.gmail.com>
Piotr Krukowiecki <piotr.krukowiecki@gmail.com> writes:
> At this moment I'm not sure myself if I consider this a bug or not.

This definitely is not a bug but is a designed and intended behaviour.

Think of running "git log" without "--full-history" that is limited with a pathspec as a tool to ask Git to show _one_ way (preferrably the simplest one) to explain how the current contents in paths that match the pathspec came to be. The "just explain to me one way" is not about machine performance but reducing the clutter in the output to help human reader(s) reading an otherwise complex history.

Previous: Piotr KrukowieckiNext: Piotr Krukowiecki
Message 4 of 5 in “git-log on a file, and merges”
  1. Piotr KrukowieckiAug 2, 2019
  2. Derrick StoleeAug 2, 2019
  3. Piotr KrukowieckiAug 2, 2019
  4. Junio C HamanoAug 2, 2019
  5. Piotr KrukowieckiAug 3, 2019

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.