git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: demerphq <demerphq@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git <git@vger.kernel.org>
Subject: Re: should git rev-parse -q --verify on a range produce output?
Date: Mon, 9 Jan 2023 10:04:13 +0100	[thread overview]
Message-ID: <CANgJU+VsAZ6Dz05ZFRQfGLgti7WssdYqGaEYEQuACoCdN+nvew@mail.gmail.com> (raw)
In-Reply-To: <xmqqpmbowek7.fsf@gitster.g>

On Mon, 9 Jan 2023 at 04:51, Junio C Hamano <gitster@pobox.com> wrote:
>
> 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.

Ok, I'll wait a bit to see if someone can suggest a good alternative
behavior, and if nobody does ill write a doc patch.

Cheers!
Yves

-- 
perl -Mre=debug -e "/just|another|perl|hacker/"

      reply	other threads:[~2023-01-09  9:11 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
2023-01-09  9:04       ` demerphq [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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CANgJU+VsAZ6Dz05ZFRQfGLgti7WssdYqGaEYEQuACoCdN+nvew@mail.gmail.com \
    --to=demerphq@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).