Re: should git rev-parse -q --verify on a range produce output?

From: Junio C Hamano <gitster@pobox.com>
Date: Jan 9, 2023, 03:51 UTC
Message-ID: <xmqqpmbowek7.fsf@gitster.g>
In-Reply-To: <CANgJU+UeZJP=tBx7ALd8_X=b25RkAdQ1NkQpueSL-p+kpCO17Q@mail.gmail.com>

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.