Jeff King <p...@peff.net> writes: > Hmm. I would have thought --no-short would just set it to LONG. That is, > we are no longer NONE at that point, as the user has told us something > on the command line. So we are whatever --no-short is, which is LONG. > > But I guess that would wreck > > git status --no-short -z > > which currently defaults to porcelain. Which, to be honest, seems a > little crazy to me, but I guess there is no reason to break it. > > I am just trying to prevent the future maintenance confusion where a > reader of the code says "Huh? What is the difference between NONE and > UNSPECIFIED?"
Yeah, I share your sentiment, but I did not think of a better way to do this without unnecessarily changing behaviour. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
