Shawn Bohrer <shawn.bohrer@xxxxxxxxx> writes: > Nope the problem Johannes Sixt was having was that he mistakenly ran > > git clean -n /*foo > > Now that isn't what he meant to do, but I figured it might be possible > that someone has their whole filesystem in a git repository, or maybe > is using some sort of chroot on their repository. Your malformed > paths guess is probably much more likely to occur. That is not a user error from the syntax point of view (although it might be from the semantics point of view). I think the caller of the excluded() function (that is probably somewhere in builtin-clean.c -- I did not check) is responsible for not supplying such a path to the called function. - 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
