Nope, it was a bug in my pre-commit hook. See the other response to this
message.
Robert Irelan | Server Systems | Epic | (608) 271-9000
-Original Message-
From: Torsten Bögershausen [mailto:tbo...@web.de]
Sent: Tuesday, March 05, 2013 4:41 AM
To: Robert Irelan
Cc: git@vger.kernel.org
hich I had not
previously committed to this repo, which is why I only ran into the
problem now. I fixed it by changing the read command to
`read -r -d '' f`, which now has the crucial space between -d and
its argument, making the zero-length string a separate argument.
Robert Ir
mmit manually. This is how I've worked
around the problem for now, and I've moved the repository that's
exhibiting problems to another directory and started work on the cloned
copy.
Why is this spurious path appearing in the index? Is it a bug, or a
symptom that my repo has been someh
3 matches
Mail list logo