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

Re: [RFC v2] blame: new option --prefer-first to better handle merged cherry-picks

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 14, 2014, 01:00 UTC
Message-ID
<xmqq7ga35qdd.fsf@gitster.dls.corp.google.com>
In-Reply-To
<xmqqbnzf5vvu.fsf@gitster.dls.corp.google.com>
Junio C Hamano <gitster@pobox.com> writes:
Show 5 quoted lines
>> While the result is more consistent and more predictable in the case
>> of merged cherry picks, it is also slower in every case.
>
> Consistent and predictable, perhaps, but I am not sure "exact" would
> be a good word.

Another thing I am not enthusiasitc about this change is that I am afraid that this may make "git blame -- path" and "git log -- path" work inconsistenly. The both cull side branches whenever one of the parents gave the resulting blob, even that parent is not the first one. But "git blame --prefer-first -- path", afaict, behaves quite differently from "git log --first-parent -- path", even though they share similar option names, adding more to the confusion.

Previous: Junio C HamanoNext: Junio C Hamano
Message 5 of 7 in “[RFC v2] blame: new option --prefer-first to better handle merged cherry-picks”
  1. Bernhard R. LinkJan 13, 2014
  2. Junio C HamanoJan 13, 2014
  3. Bernhard R. LinkJan 13, 2014
  4. Junio C HamanoJan 13, 2014
  5. Junio C HamanoJan 14, 2014
  6. Junio C HamanoJan 14, 2014
  7. Junio C HamanoJan 14, 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.