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

Re: Reverting the whole index-base series

From
Junio C Hamano <junkio@cox.net>
Date
Apr 15, 2007, 23:39 UTC
Message-ID
<7vhcrh1a2w.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<Pine.LNX.4.64.0704151632140.5473@woody.linux-foundation.org>
Linus Torvalds <torvalds@linux-foundation.org> writes:
Show 20 quoted lines
> On Sun, 15 Apr 2007, Junio C Hamano wrote:
>> >
>> > But no, I wasn't following that series, so I probably totally 
>> > misunderstood what you were going after..
>> 
>> Could be.
>> 
>> The issue in short was about:
>> 
>> 	$ git checkout $branch
>> 
>> At this point you think your HEAD is at $branch head, and you
>> are working towards building a commit that has that commit as
>> one of the parents.
>> 
>> Then a gremlin updates the commit HEAD points at.
>
> Ahh, ok. I was kind of expecting that you'd actually do something at 
> "receive-pack" time instead, not at the next commit. That would also solve 
> it - just have an option saying "update the working tree when receiving". 

I specifically did not want to do that, as it would break existing workflow of pushing into a live repository, knowing the branch might be checked out at the remote.

Also, the case of multiple working trees sharing the same refs/ namespace cannot be solved by trapping receive-pack alone.

Previous: Linus TorvaldsNext: Linus Torvalds
Message 12 of 15 in “Some index-base bug in "next" branch ("git-applymbox"-related?)..”
  1. Linus TorvaldsApr 12, 2007
  2. Junio C HamanoApr 12, 2007
  3. Junio C HamanoApr 13, 2007
  4. Linus TorvaldsApr 13, 2007
  5. Junio C HamanoApr 13, 2007
  6. Linus TorvaldsApr 13, 2007
  7. Junio C HamanoApr 13, 2007
  8. Reverting the whole index-base seriesJunio C Hamano, Apr 15, 2007
  9. Linus TorvaldsApr 15, 2007
  10. Junio C HamanoApr 15, 2007
  11. Linus TorvaldsApr 15, 2007
  12. Junio C HamanoApr 15, 2007
  13. Linus TorvaldsApr 15, 2007
  14. Junio C HamanoApr 16, 2007
  15. Linus TorvaldsApr 16, 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.