From: Junio C Hamano <gitster@pobox.com>
To: Pushkar Singh <pushkarkumarsingh1970@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v4 0/1] subtree: validate --prefix against commit in split
Date: Fri, 23 Jan 2026 09:37:25 -0800 [thread overview]
Message-ID: <xmqqwm18grhm.fsf@gitster.g> (raw)
In-Reply-To: <20260123142658.15516-2-pushkarkumarsingh1970@gmail.com> (Pushkar Singh's message of "Fri, 23 Jan 2026 14:26:56 +0000")
Pushkar Singh <pushkarkumarsingh1970@gmail.com> writes:
> Changes in v4:
> * fix indentation in the case statement
> * add a regression test to ensure --prefix is validated against the
> target commit rather than the working tree
>
> No functional changes beyond the above.
This seems to be identical to v3, which already had the fix to the
case and addition of tests.
https://lore.kernel.org/git/20260115175403.3971-3-pushkarkumarsingh1970@gmail.com/
next prev parent reply other threads:[~2026-01-23 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 14:26 [PATCH v4 0/1] subtree: validate --prefix against commit in split Pushkar Singh
2026-01-23 14:35 ` [PATCH v4 1/1] " Pushkar Singh
2026-01-23 17:37 ` Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-23 17:47 [PATCH v4 0/1] " Pushkar Singh
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=xmqqwm18grhm.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=pushkarkumarsingh1970@gmail.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