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

Re: [PATCH v2] log: improve --follow following renames for non-linear history

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 12, 2026, 20:10 UTC
Message-ID
<xmqqa4szh644.fsf@gitster.g>
In-Reply-To
<aipTOsH8LKTSwglj@collabora.com>
Miklos Vajna <vmiklos@collabora.com> writes:
Show 7 quoted lines
>  Documentation/config/log.adoc |   3 +-
>  log-tree.c                    | 133 ++++++++++++++++++++++++++++++++++
>  log-tree.h                    |   1 +
>  revision.c                    |   2 +
>  revision.h                    |   4 +
>  t/meson.build                 |   1 +
>  t/t4218-log-follow-merge.sh   | 119 ++++++++++++++++++++++++++++++

t4218 seems to be taken by another topic in-flight, so this needs renumbering.

Previous: Miklos VajnaNext: Miklos Vajna
Message 13 of 18 in “log: let --follow follow renames in merge commits”
  1. log: let --follow follow renames in merge commitsMiklos Vajna, May 12, 2026
  2. Miklos VajnaMay 19, 2026
  3. Junio C HamanoMay 19, 2026
  4. Junio C HamanoMay 19, 2026
  5. log: improve --follow following renames for non-linear historyMiklos Vajna, Jun 8, 2026
  6. Junio C HamanoJun 8, 2026
  7. log: improve --follow following renames for non-linear historyMiklos Vajna, Jun 11, 2026
  8. Junio C HamanoJun 11, 2026
  9. log: improve --follow following renames for non-linear historyMiklos Vajna, Jun 15, 2026
  10. log: improve --follow following renames for non-linear historyMiklos Vajna, Jun 22, 2026
  11. Junio C HamanoJun 22, 2026
  12. Miklos VajnaJun 23, 2026
  13. Junio C HamanoJun 12, 2026
  14. Miklos VajnaMay 20, 2026
  15. Jeff KingMay 22, 2026
  16. log: improve --follow following renames in merge commitsMiklos Vajna, May 23, 2026
  17. Miklos VajnaMay 30, 2026
  18. Miklos VajnaJun 4, 2026

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.