Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Miklos Vajna <vmiklos@collabora.com>
Cc: Jeff King <peff@peff.net>,  git@vger.kernel.org
Subject: Re: [PATCH v2] log: improve --follow following renames for non-linear history
Date: Fri, 12 Jun 2026 13:10:51 -0700	[thread overview]
Message-ID: <xmqqa4szh644.fsf@gitster.g> (raw)
In-Reply-To: <aipTOsH8LKTSwglj@collabora.com> (Miklos Vajna's message of "Thu, 11 Jun 2026 08:18:34 +0200")

Miklos Vajna <vmiklos@collabora.com> writes:

>  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.

  parent reply	other threads:[~2026-06-12 20:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-12  7:21 [PATCH] log: let --follow follow renames in merge commits Miklos Vajna
2026-05-19  6:17 ` Miklos Vajna
2026-05-19  6:37   ` Junio C Hamano
2026-05-19  8:14     ` Junio C Hamano
2026-06-08  6:35       ` [PATCH] log: improve --follow following renames for non-linear history Miklos Vajna
2026-06-08 15:10         ` Junio C Hamano
2026-06-11  6:18           ` [PATCH v2] " Miklos Vajna
2026-06-11 22:32             ` Junio C Hamano
2026-06-12 20:10             ` Junio C Hamano [this message]
2026-05-20 13:28     ` [PATCH] log: let --follow follow renames in merge commits Miklos Vajna
2026-05-22  5:43       ` Jeff King
2026-05-23  6:04         ` [PATCH] log: improve --follow following " Miklos Vajna
2026-05-30  6:28           ` Miklos Vajna
2026-06-04 12:20             ` Miklos Vajna

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqa4szh644.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=vmiklos@collabora.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox