"Ping Yin" <pkufranky@xxxxxxxxx> writes: > Following scripts can reproduce the problem: in the final line, > foo.txt is generated in bare foo.git > # reset bare and then push > cd foo.git && git reset --hard HEAD^ && cd .. "git reset" is about resetting *both* the branch tip and the work tree. Doesn't it create unwanted work tree files when misused this way at this point already? > cd foo && git push && cd .. "git push" never touches the work tree. It is possible that there is a PEBCAK hook enabled in that bare repository that creates random files upon receiving a push, but that is hardly worth reporting _here_ on the list ;-). Puzzled... - 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
