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

Re: Bug: "git checkout -b" should be allowed in empty repo

From
Michael Haggerty <mhagger@alum.mit.edu>
Date
Jan 31, 2012, 08:57 UTC
Message-ID
<4F27ACED.2050709@alum.mit.edu>
In-Reply-To
<7v39axc9gp.fsf@alter.siamese.dyndns.org>
On 01/30/2012 07:48 PM, Junio C Hamano wrote:
Show 15 quoted lines
> Michael Haggerty <mhagger@alum.mit.edu> writes:
> 
>> [3] If commit 0000000 were treated specially, then there would be no
>> unborn branches but only branches pointing at the empty commit.  In that
>> case, my expectation would change--the old branch should be left
>> pointing at 0000000.  But currently git has no concept of an unborn
>> branch that is not HEAD.
> 
> And it probably is not a good thing to add such. Under that constraints,
> HEAD that says refs/heads/foo where foo does not exist yet needs to be
> special cased at places where it matters.
> 
> For that matter, even if we artificially created refs/heads/foo before any
> commit is made and made it point at 0{40}, you would need to add special
> cases to other parts of the system

No, the idea is to avoid special casing by making 0{40} into a real (but empty) revision.

> (e.g. "commit" needs to notice that the
> result should be a root, not a child of 0{40};

No, commits that were previously generated as orphans *would* now be generated as children of the special 0{40} commit.

> "checkout other_branch"
> needs to notice that it should refrain from running the equivalent of
> "read-tree -m HEAD other_branch" because HEAD does not point at a real
> tree;

No, it would merge the 0{40} commit with other_branch like usual, resulting in the same contents as other_branch. Indeed, if other_branch is also ultimately a descendant of 0{40}, this would be like a fast-forward merge.

> etc.
This "etc" might include problems.
> so it does not change the fact that the unborn branch is case
> is special.

On the contrary, I believe that much special casing could be eliminated and the UI made more uniform by treating everything as a descendant of a special "NULL" commit.

Michael
-- 
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
Previous: Jeff KingNext: Johannes Sixt
Message 30 of 34 in “Bug: "git checkout -b" should be allowed in empty repo”
  1. Michael HaggertyJan 29, 2012
  2. Junio C HamanoJan 29, 2012
  3. Junio C HamanoJan 29, 2012
  4. Michael HaggertyJan 30, 2012
  5. Junio C HamanoJan 30, 2012
  6. Junio C HamanoJan 30, 2012
  7. Jeff KingJan 30, 2012
  8. Junio C HamanoFeb 6, 2012
  9. Junio C HamanoFeb 6, 2012
  10. Jeff KingFeb 6, 2012
  11. Andrew ArdillFeb 6, 2012
  12. Jeff KingFeb 6, 2012
  13. Michael HaggertyFeb 6, 2012
  14. Jeff KingFeb 6, 2012
  15. Junio C HamanoFeb 6, 2012
  16. Jeff KingFeb 6, 2012
  17. Michael HaggertyFeb 7, 2012
  18. demerphqFeb 6, 2012
  19. Junio C HamanoFeb 6, 2012
  20. Jeff KingFeb 6, 2012
  21. Junio C HamanoFeb 6, 2012
  22. Junio C HamanoFeb 6, 2012
  23. Jeff KingFeb 6, 2012
  24. Michael HaggertyFeb 6, 2012
  25. Junio C HamanoFeb 6, 2012
  26. Jeff KingJan 30, 2012
  27. branch --edit-description: protect against mistyped branch nameJunio C Hamano, Feb 6, 2012
  28. Junio C HamanoFeb 6, 2012
  29. Jeff KingFeb 6, 2012
  30. Michael HaggertyJan 31, 2012
  31. Johannes SixtJan 31, 2012
  32. demerphqJan 31, 2012
  33. Jakub NarebskiJan 31, 2012
  34. Michael HaggertyJan 31, 2012

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.