On Sat, 10 Feb 2007, Johannes Schindelin wrote: > So, what is the big problem about accepting that patching git-status for > one obscure use is wrong, wrong, wrong, when git-diff already does what is > needed??? Because git-status itself is conceptually a read-only operation, and having it barf on a read-only file system is justifiably a bug. But I agree that attempting to fix it now is probably just too risky not to compromize the 1.5.0 release. Better leave it as a known issue for v1.5.0 and fix it later... especially if there is a possible workaround in the mean time. Nicolas - 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