git config --get-regexp exit status

From: David Kågedal <davidk@lysator.liu.se>
Date: Dec 13, 2007, 13:42 UTC
Message-ID: <871w9qsoc8.fsf@lysator.liu.se>
In-Reply-To: <20071213133653.13925.89254.stgit@krank>

David Kågedal <davidk@lysator.liu.se> writes:

Show 5 quoted lines

> I made a patch that uses "git config --get-regexp" to get the
> description and stgit.stackformatversion options for all branches at
> once, and ignore the "protected" flag that I don't use. With this
> change, I'm almost down to half a second, which almost makes it
> usable.

One thing that annoyed me what that "git config --get-regexp" will return zero, one, or more matches, which are all valid reponses. But it treats the zero-match special and return an exit status of 1.

Is that a conscious choice, or just an effect of how "git config --get" works?

Since zero matches isn't really an error, I would like the exit status to be 0. At least for this use case :-)

-- 
David Kågedal