Hi, On Wed, 16 Jul 2008, Dmitry Potapov wrote: > On Wed, Jul 16, 2008 at 3:54 PM, Dmitry Potapov <dpotapov@xxxxxxxxx> wrote: > > > > For instance, git show will show you nothing at all and exit with 0. > > The same problem with git whatchanged. The whole history mysteriously > > disappeared at that commit, and git whatchanged exited with 0 without > > any error or warning... Though git log will show you all history, but > > if you run it with -p then it will also exit with zero at this commit > > silently like previously history do not exist at all. > > It turned out that git actually crashed while doing diff, but because it > was a forked process, the parent exited normally with code 0. I wonder > should not the parent process to exit with a non-zero code if the child > died by SIGSEG or another signal? We'll probably need to use the MinGW pager handling for Unix, too, and check for a died child. Not overly trivial, though. Ciao, Dscho -- 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
