git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Nguyen Thai Ngoc Duy <pclouds@gmail.com>,
	Nikolay Vladimirov <nikolay@vladimiroff.com>,
	git@vger.kernel.org
Subject: Re: [PATCH] buitin_config: return postitive status in get_value
Date: Sun, 29 Jul 2012 17:41:17 -0400	[thread overview]
Message-ID: <20120729214117.GB3071@sigill.intra.peff.net> (raw)
In-Reply-To: <7v4noqwb6e.fsf@alter.siamese.dyndns.org>

On Sun, Jul 29, 2012 at 01:43:21PM -0700, Junio C Hamano wrote:

> > But if we really want to follow that "documented" subset of possible
> > conditions, I agree that your version to return "1" in this case,
> > together with a change to initialize "ret" to "7" and document it as
> > "all other errors (ret=7), would make more sense.  Other conditions
> > that have been added since that partial enumeration of the exit code
> > was done are regexp errors, which I think will get -1 from the same
> > function.
> 
> IOW, something like this.
> 
>  Documentation/git-config.txt | 18 ++++++++++--------
>  builtin/config.c             |  8 ++++++--
>  2 files changed, 16 insertions(+), 10 deletions(-)

This looks right to me. Even if we are missing an error case, it is
certainly going in the right direction.

-Peff

  reply	other threads:[~2012-07-29 21:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-28 11:42 [PATCH] buitin_config: return postitive status in get_value Nikolai Vladimirov
2012-07-28 12:59 ` Nguyen Thai Ngoc Duy
2012-07-28 13:18   ` Nikolay Vladimirov
2012-07-28 13:29     ` Nguyen Thai Ngoc Duy
2012-07-29  6:38       ` Junio C Hamano
2012-07-29 20:43         ` Junio C Hamano
2012-07-29 21:41           ` Jeff King [this message]
2012-07-30 12:26           ` Nguyen Thai Ngoc Duy
2012-07-30 15:51             ` Junio C Hamano
2012-07-29 21:39         ` Jeff King

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=20120729214117.GB3071@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=nikolay@vladimiroff.com \
    --cc=pclouds@gmail.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).