From: Junio C Hamano <gitster@pobox.com>
To: "Ping Yin" <pkufranky@gmail.com>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: [bug] Working files created in bare repository when pushing to a rewound bare repository
Date: Sun, 30 Dec 2007 22:50:29 -0800 [thread overview]
Message-ID: <7vd4sn73yi.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <46dff0320712302242m34b5267dlb3f26488293d5d51@mail.gmail.com> (Ping Yin's message of "Mon, 31 Dec 2007 14:42:42 +0800")
"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...
prev parent reply other threads:[~2007-12-31 6:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-31 6:42 [bug] Working files created in bare repository when pushing to a rewound bare repository Ping Yin
2007-12-31 6:47 ` Jeff King
2007-12-31 7:02 ` Ping Yin
2007-12-31 7:07 ` Jeff King
2007-12-31 7:13 ` Jeff King
2007-12-31 7:19 ` Jeff King
2007-12-31 7:26 ` Jeff King
2008-01-03 21:29 ` Junio C Hamano
2007-12-31 6:50 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vd4sn73yi.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=pkufranky@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).