On Fri, Apr 02, 2010 at 09:37:03PM +0100, Markus Heidelberg wrote: > > Does this mean we will fail to run in a read-only repository? > > You're right. > But that was already the case when "status" was "commit --dry-run". > I have to admit, I didn't think about this scenario, but simply looked > for the differences between these two commands. Sort of. See ab68545 (status: don't require the repository to be writable, 2010-01-19), which went onto maint while the "status is no longer commit --dry-run" topic was cooking elsewhere. So I think it would be a regression from 1.6.6.2 onwards. At any rate, I think we all agree on what it _should_ do, so if you're willing to do an updated patch, that would be great. The patch from ab68545 may be helpful, as the code it changed is quite similar to what you posted in this series. -Peff -- 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