> From: "Philip Oakley" <philipoak...@iee.org>
> > Unfortunately, it was set off by a cron job, and I have cron jobs
> > doing Git archiving of large parts of my file system, and there are
> > certainly circular symlinks hidden in various places.
> Definately worth looking then ;-)
I've got a reproducible test case now, and for the entire stack of
"git status" processes, I have their CWDs, command lines, and
environments. So I should be able to trace git-status and determine
exactly how it is freaking out.
There may be some submodule issues involved -- the repository is not
in the top level directory, but core.worktree is '/', and at least
some messages I'm seeing suggest that Git sees the repository as a
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.