From: Junio C Hamano <gitster@pobox.com>
Date: Mon, 31 Dec 2007 06:50:29 GMT
Subject: Re: [bug] Working files created in bare repository when pushing to a rewound bare repository
Message-ID: <7vd4sn73yi.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <46dff0320712302242m34b5267dlb3f26488293d5d51@mail.gmail.com>

"Ping Yin" <pkufranky@gmail.com> 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...