public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Deveshi Dwivedi <deveshigurgaon@gmail.com>,
	 Victoria Dye <vdye@github.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] t1006: fix %(rest) test for object names with whitespace
Date: Thu, 19 Feb 2026 19:30:19 -0800	[thread overview]
Message-ID: <xmqqldgo148k.fsf@gitster.g> (raw)
In-Reply-To: <xmqqzf5431ek.fsf@gitster.g> (Junio C. Hamano's message of "Thu, 19 Feb 2026 12:48:35 -0800")

Junio C Hamano <gitster@pobox.com> writes:

> I agree that fixing underlying issue would be a much more valuable
> outcome of resolving that FIXME comment, but isn't the approach to
> give $object_name fundamentally incompatible with %(rest), making
> the issue something %(rest) implementation cannot "fix", is it?
>
> That is a part of the reason why I said I am dubious about the FIXME
> comment in my comment.

Actually, it is worse than that.

We already _promise_ to chop the input line at the first whitespace
boundary in our documentation when we use %(rest), so there is
nothing we can do to "fix" on the implementation side.  What your
original tested, i.e., if the early part of the input up to the
first whitespace does *not* name an object, then the test cannot
succeed (not just that, the test should fail, unless it happens to
name another valid object), is the advertised behaviour of this
feature.

Thanks.

  reply	other threads:[~2026-02-20  3:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-19 15:24 [PATCH] t1006: fix %(rest) test for object names with whitespace Deveshi Dwivedi
2026-02-19 19:50 ` Junio C Hamano
2026-02-19 20:23   ` Victoria Dye
2026-02-19 20:48     ` Junio C Hamano
2026-02-20  3:30       ` Junio C Hamano [this message]
2026-02-20 16:59         ` Deveshi Dwivedi

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=xmqqldgo148k.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=deveshigurgaon@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=vdye@github.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