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

Re: Working copy revision and push pain

From
JWJonathan Watt <jwatt@jwatt.org>
Date
Mar 23, 2008, 14:48 UTC
Message-ID
<47E66DAA.4080807@jwatt.org>
In-Reply-To
<alpine.LSU.1.00.0803231519380.4353@racer.site>
Johannes Schindelin wrote:
Show 10 quoted lines
>> The end result is that HEAD is always the most recent commit to which 
>> your working copy is relative to.  See also 
>> http://www.kernel.org/pub/software/scm/git/docs/glossary.html
>>
>> So, it sounds like we're both saying that in your case, you'd like the
>> HEAD become detached and track the sha1 that it previously pointed to
>> before your push rather than continuing to track the updated branch.
> 
> If you ever propose to detach the HEAD in a remote repository when 
> somebody pushed into the referenced branch, I am totally opposed to that.

The alternative is to leave the working copy in a totally broken state. I'm not sure why that would be preferable.

> You can play your own games with the update and post-update hooks as much 
> as you want, but please leave official Git alone.  Thankyouverymuch.

My hope here is for a reduction in the pain/time taken out from real work in the OSS developer world while people are moving to DSCMs - particularly for those that have to learn/move between both Mercurial and git. Requiring people to be aware of this gotcha and to use solutions like hooks seems to raise barriers rather than eliminate them.

Cloning and working with multiple repositories locally is a particularly Mercurial workflow. I see this issue as a barrier to those who've cut their DSCM teeth on Mercurial and are trying to use git. Would detaching HEAD really be a problem in git workflows?

Jonathan
Previous: Johannes SchindelinNext: Johannes Schindelin
Message 8 of 32 in “Working copy revision and push pain”
  1. Jonathan WattMar 23, 2008
  2. Johannes SchindelinMar 23, 2008
  3. Jonathan WattMar 23, 2008
  4. Elijah NewrenMar 23, 2008
  5. Jonathan WattMar 23, 2008
  6. Elijah NewrenMar 23, 2008
  7. Johannes SchindelinMar 23, 2008
  8. Jonathan WattMar 23, 2008
  9. Johannes SchindelinMar 23, 2008
  10. Jonathan WattMar 23, 2008
  11. Johannes SchindelinMar 23, 2008
  12. Auto detaching head options (Re: Working copy revision and push pain)Jan Hudec, Mar 25, 2008
  13. Johannes SchindelinMar 25, 2008
  14. Jeff KingMar 25, 2008
  15. Junio C HamanoMar 26, 2008
  16. Auto detaching head options (update) (Re: Working copy revision and push pain)Jan Hudec, Mar 29, 2008
  17. Jeff KingMar 29, 2008
  18. Junio C HamanoMar 31, 2008
  19. Jeff KingMar 31, 2008
  20. Jeff KingMar 31, 2008
  21. Elijah NewrenMar 23, 2008
  22. Jonathan WattMar 23, 2008
  23. Johannes SchindelinMar 23, 2008
  24. Johan HerlandMar 23, 2008
  25. Jonathan WattMar 23, 2008
  26. Junio C HamanoMar 23, 2008
  27. Junio C HamanoMar 23, 2008
  28. Johannes SchindelinMar 23, 2008
  29. Johannes SchindelinMar 24, 2008
  30. Johan HerlandMar 24, 2008
  31. Johannes SchindelinMar 23, 2008
  32. Jonathan WattMar 23, 2008

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.