From: Junio C Hamano <gitster@pobox.com>
To: Stanislav Aleksandrov <lightofmysoul@gmail.com>
Cc: git@vger.kernel.org, Patrick Steinhardt <ps@pks.im>,
Adrian Ratiu <adrian.ratiu@collabora.com>,
Jacob Keller <jacob.keller@gmail.com>, Jeff King <peff@peff.net>
Subject: Re: [RFC PATCH] submodule: make '^/' work like '../' but with an absolute path
Date: Sat, 31 Oct 2026 08:54:19 -0700 [thread overview]
Message-ID: <xmqq1p9550ic.fsf@gitster.g> (raw)
In-Reply-To: <20261030150739.3855910-1-lightofmysoul@gmail.com> (Stanislav Aleksandrov's message of "Fri, 30 Oct 2026 15:07:39 +0000")
Stanislav Aleksandrov <lightofmysoul@gmail.com> writes:
> Junio C Hamano <gitster@pobox.com> writes:
>
>> One bad news is that t7427 is taken by another topic in flight, and
>> this topic will break tests when merged to 'seen'. I'll try moving
>> it to t7428 before queuing, but when a new iteration of the patch is
>> posted, please make sure to check (1) it applies cleanly to 'master',
>> (2) the result of (1) merges cleanly to 'next' and 'seen', and all
>> three pass all tests (not just 0060, 7428, and 7450).
>
> Thanks for fixing the test number. The t7428 squash looks good to me,
> please squash it in.
I'll keep them separate, as the fix-up will become unnecessary as
long as you remember the need for it when the patch leaves RFC
status; the test number crashing would not be the only thing that
needs fixing, I presume.
prev parent reply other threads:[~2026-10-31 15:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 18:51 [RFC PATCH] submodule: make '^/' work like '../' but with an absolute path Stanislav Aleksandrov
2026-10-25 19:42 ` Jacob Keller
2026-10-25 21:25 ` Stanislav Aleksandrov
2026-10-25 23:11 ` Jacob Keller
2026-10-30 15:08 ` Stanislav Aleksandrov
2026-10-27 17:39 ` Junio C Hamano
2026-10-30 15:07 ` Stanislav Aleksandrov
2026-10-31 15:54 ` Junio C Hamano [this message]
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=xmqq1p9550ic.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=adrian.ratiu@collabora.com \
--cc=git@vger.kernel.org \
--cc=jacob.keller@gmail.com \
--cc=lightofmysoul@gmail.com \
--cc=peff@peff.net \
--cc=ps@pks.im \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.