David Kågedal <davidk@xxxxxxxxxxxxxx> writes: > 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 - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
