From: Toon Claes <toon@iotcl•com>
To: Eric Sunshine <sunshine@sunshineco•com>
Cc: git@vger•kernel.org
Subject: Re: [PATCH 1/1] builtin/show-ref: treat directory directory as non-existing in --exists
Date: Wed, 10 Jan 2024 16:20:41 +0100 [thread overview]
Message-ID: <874jflfc26.fsf@iotcl.com> (raw)
In-Reply-To: <CAPig+cTRHHJ3pzWJtVJf8rKhvAJFYqrO0JsyTRTi6T5s+gznDg@mail.gmail.com>
Eric Sunshine <sunshine@sunshineco•com> writes:
> It may not be worth a reroll, but I found the explanation you gave in
> the cover letter more illuminating than what is written above for
> explaining why this change is desirable. In particular, the discussion
> of the reftable backend was very helpful.
Well, I wasn't sure the explanation would be relevant in the present,
because the reftable backend might happen relatively far into the
future.
--
Toon
next prev parent reply other threads:[~2024-01-10 15:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 14:15 [PATCH 0/1] Fix error message in git-show-ref(1) --exists Toon Claes
2024-01-10 14:15 ` [PATCH 1/1] builtin/show-ref: treat directory directory as non-existing in --exists Toon Claes
2024-01-10 14:36 ` Eric Sunshine
2024-01-10 15:20 ` Toon Claes [this message]
2024-01-17 6:29 ` Patrick Steinhardt
2024-01-17 23:07 ` Junio C Hamano
2024-01-18 8:24 ` Toon Claes
2024-01-18 19:19 ` Junio C Hamano
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=874jflfc26.fsf@iotcl.com \
--to=toon@iotcl$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=sunshine@sunshineco$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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