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
Jeff King <peff@peff.net>
Date
Feb 6, 2012, 05:45 UTC
Message-ID
<20120206054558.GA7883@sigill.intra.peff.net>
In-Reply-To
<7vk440a5qw.fsf@alter.siamese.dyndns.org>
On Sun, Feb 05, 2012 at 09:30:15PM -0800, Junio C Hamano wrote:
Show 27 quoted lines
> Jeff King <peff@peff.net> writes:
> 
> > Sure, that's one way to do it. But I don't see any point in not allowing
> > "git checkout -b" to be another way of doing it. Is there some other use
> > case for "git checkout -b" from an unborn branch? Or is there some
> > harmful outcome that can come from doing so that we need to be
> > protecting against? Am I missing something?
> 
> Mostly because it is wrong at the conceptual level to do so.
> 
> 	git checkout -b foo
> 
> is a short-hand for
> 
> 	git checkout -b foo HEAD
> 
> which is a short-hand for
> 
> 	git branch foo HEAD &&
>         git checkout foo
> 
> But the last one has no chance of working if you think about it, because
> "git branch foo $start" is a way to start a branch at $start and you need
> to have something to point at with refs/heads/foo.
> 
> So we are breaking the equivalence between these three only when HEAD
> points at an unborn branch.

I think it is only wrong at the conceptual level because you have specified the concepts in such a way that it is so. That is how git does it _now_, but the whole point of this is to change git's behavior to handle a potentially useful special case. I could also say this: "git checkout -b foo HEAD" does two things:

  1. create a new branch "foo" pointing to the current sha1 of HEAD
  2. point the HEAD symref at refs/heads/foo
And then the proposed behavior might amend the first point to say:
  1. if HEAD points to an existing ref, then create a new branch...

which is perfectly consistent and simple. It does violate your "X is a short-hand for Y" above, but why is that a bad thing? It seems you are arguing against a special case _because_ it is a special case, not because it is not a reasonable thing to do or expect.

Anyway. I am still not convinced that this is even a useful thing to want to do, so I am certainly not volunteering to write such a patch. So perhaps there is no point arguing about it.

-Peff
Previous: Junio C HamanoNext: Michael Haggerty
Message 23 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.