git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [bug] Working files created in bare repository when pushing to a rewound bare repository

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 31, 2007, 06:50 UTC
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...
Previous: Junio C Hamano
Message 9 of 9 in “[bug] Working files created in bare repository when pushing to a rewound bare repository”
  1. Ping YinDec 31, 2007
  2. Jeff KingDec 31, 2007
  3. Ping YinDec 31, 2007
  4. Jeff KingDec 31, 2007
  5. Jeff KingDec 31, 2007
  6. Jeff KingDec 31, 2007
  7. Jeff KingDec 31, 2007
  8. Junio C HamanoJan 3, 2008
  9. Junio C HamanoDec 31, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.