Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> writes: > 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. - 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