git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Keller\, Jacob E" <jacob.e.keller@intel.com>
Cc: "git\@vger.kernel.org" <git@vger.kernel.org>,
	"peff\@peff.net" <peff@peff.net>,
	"sunshine\@sunshineco.com" <sunshine@sunshineco.com>
Subject: Re: [PATCH 3/3] tag: support configuring --sort via .gitconfig
Date: Tue, 15 Jul 2014 12:10:57 -0700	[thread overview]
Message-ID: <xmqqlhruv3ni.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <xmqq7g3ewkp8.fsf@gitster.dls.corp.google.com> (Junio C. Hamano's message of "Tue, 15 Jul 2014 11:17:23 -0700")

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

> "Keller, Jacob E" <jacob.e.keller@intel.com> writes:
>
>> On Tue, 2014-07-15 at 09:03 -0700, Junio C Hamano wrote:
>> ...
>>> >> Yes, that is fun.
>>> >> 
>>> >> I actually think your "In 'version:pefname' and 'wersion:refname',
>>> >> we want be able to report 'pefname' and 'wersion' are misspelled,
>>> >> and returning -1 or enum would not cut it" is a good argument.  The
>>> >> callee wants to have flexibility on _what_ to report, just as the
>>> >> caller wants to have flexibility on _how_.  In this particular code
>>> >> path, I think the former far outweighs the latter, and my suggestion
>>> >> I called "silly" might not be so silly but may have struck the right
>>> >> balance.  I dunno.
>> ...
>> I agree. But what about going back to the older setup where the caller
>> can output correct error message? I'm ok with using an enum style
>> return, to be completely honest. I would prefer this, actually.
>
> Depends on which older setup you mean, I think.  The one that does
> not let us easily give more context dependent diagnoses that lets us
> distinguish between version:pefname and version:refname by returning
> only -1 or an enum?

In case it was not clear, I do not think -1 or enum is a good idea.

  parent reply	other threads:[~2014-07-15 19:11 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-11 22:55 [PATCH 1/3] tag: use skip_prefix instead of magic numbers Jacob Keller
2014-07-11 22:55 ` [PATCH 2/3] tag: fix --sort tests to use cat<<-\EOF format Jacob Keller
2014-07-11 22:55 ` [PATCH 3/3] tag: support configuring --sort via .gitconfig Jacob Keller
2014-07-13  3:29   ` Eric Sunshine
2014-07-13 17:10     ` Junio C Hamano
2014-07-13 17:33       ` Jeff King
2014-07-13 18:36         ` Jeff King
2014-07-14 17:17           ` Junio C Hamano
2014-07-15 14:52             ` Keller, Jacob E
2014-07-15 16:03               ` Junio C Hamano
2014-07-15 17:27                 ` Keller, Jacob E
2014-07-15 18:17                   ` Junio C Hamano
2014-07-15 18:31                     ` Keller, Jacob E
2014-07-15 19:12                       ` Junio C Hamano
2014-07-15 20:29                         ` Keller, Jacob E
2014-07-15 21:31                         ` Keller, Jacob E
2014-07-15 19:10                     ` Junio C Hamano [this message]
2014-07-15 23:38                 ` Jeff King
2014-07-12  1:02 ` [PATCH 1/3] tag: use skip_prefix instead of magic numbers Jeff King
  -- strict thread matches above, loose matches on Subject: below --
2014-07-11 20:51 Jacob Keller
2014-07-11 20:51 ` [PATCH 3/3] tag: support configuring --sort via .gitconfig Jacob Keller
2014-07-11 20:54   ` Keller, Jacob E
2014-07-11 21:06   ` Jeff King
2014-07-11 21:08     ` Keller, Jacob E
2014-07-11 22:17     ` Junio C Hamano
2014-07-11 22:30       ` Keller, Jacob E

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=xmqqlhruv3ni.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jacob.e.keller@intel.com \
    --cc=peff@peff.net \
    --cc=sunshine@sunshineco.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;
as well as URLs for NNTP newsgroup(s).