From: Junio C Hamano <gitster@pobox.com>
To: demerphq <demerphq@gmail.com>
Cc: Git <git@vger.kernel.org>
Subject: Re: should git rev-parse -q --verify on a range produce output?
Date: Mon, 09 Jan 2023 12:51:36 +0900 [thread overview]
Message-ID: <xmqqpmbowek7.fsf@gitster.g> (raw)
In-Reply-To: <CANgJU+UeZJP=tBx7ALd8_X=b25RkAdQ1NkQpueSL-p+kpCO17Q@mail.gmail.com> (demerphq@gmail.com's message of "Sun, 8 Jan 2023 11:45:13 +0100")
demerphq <demerphq@gmail.com> writes:
> Is this something you think should be fixed? I would give it a go if
> there was some direction on what it should do in this case. Just error
> early and produce no output?
I do not mind if the error case gets changed to behave differently,
as long as the updated behaviour is something everybody thinks an
improvement over the current behaviour. I do not offhand know what
the "fixed" behaviour should be.
I do not mind if nothing changed and documentation gets updated to
reduce end-user confusion, either.
Thanks.
next prev parent reply other threads:[~2023-01-09 3:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 23:03 should git rev-parse -q --verify on a range produce output? demerphq
2023-01-08 2:34 ` Junio C Hamano
2023-01-08 10:45 ` demerphq
2023-01-09 3:51 ` Junio C Hamano [this message]
2023-01-09 9:04 ` demerphq
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=xmqqpmbowek7.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=demerphq@gmail.com \
--cc=git@vger.kernel.org \
/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.