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

Re: git log omits deleting merges

From
Jeff King <peff@peff.net>
Date
Mar 24, 2014, 14:19 UTC
Message-ID
<20140324141934.GA651@sigill.intra.peff.net>
In-Reply-To
<5330081C.3090403@gmail.com>
On Mon, Mar 24, 2014 at 11:25:32AM +0100, Ephrim Khong wrote:
Show 5 quoted lines
> Thank you for the explanation, I now understand why this is happening from a
> technical point of view. From a usability perspective, it is a bit confusing
> that a flag that should intuitively increase the number of shown commits
> (--follow) removes a commit from the output. Though this is just a minor
> annoyance, so no strong opinion here.

Sorry, I focused on the --diff-filter aspect of your question. As for --follow, I think that is less "by design" and more "what happens to occur, because --follow is a bit of a hack".

So there may be a bug, or room for improvement in the code there, though if the solution involves turning on diffs for all merges, that may be prohibitively expensive.

-Peff
Previous: Ephrim Khong
Message 6 of 6 in “git log omits deleting merges”
  1. Ephrim KhongFeb 20, 2014
  2. Jeff KingMar 20, 2014
  3. Philip OakleyMar 20, 2014
  4. Jeff KingMar 21, 2014
  5. Ephrim KhongMar 24, 2014
  6. Jeff KingMar 24, 2014

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.