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

Re: DWIM "git checkout frotz" to "git checkout -b frotz origin/frotz"

From
Clemens Buchacher <drizzd@aon.at>
Date
Jun 7, 2010, 18:54 UTC
Message-ID
<20100607185439.GB17343@localhost>
In-Reply-To
<buobpbnz6mh.fsf@dhlpc061.dev.necel.com>
On Mon, Jun 07, 2010 at 03:41:58PM +0900, Miles Bader wrote:
Show 8 quoted lines
> Clemens Buchacher <drizzd@aon.at> writes:
> > The suggestion above would be perfect. It is an easy and obvious
> > solution, and the user is even educated about their mistake.
> 
> Of course, having been educated as to what's going on, the user would
> then be annoyed that they had to type all those boilerplate args when
> git clearly knew what they wanted to do... and that would be the case
> every time from then on...
Why should the user make the same mistake over and over again?
Show 7 quoted lines
> I think this DWIM is actually pretty convenient, and very often does
> reflect what the user intuitively is trying to do when giving such args.
> 
> Given that git _does_ tell you what it's doing, and that it's easy
> enough to delete the new branch if it wasn't really wanted, it seems
> pretty harmless as well.  A campaign to delete this feature seems kind
> of silly...

It may be harmless to users who know what's going on. I can certainly deal with this feature, whether it's there or not.

But this is supposedly a feature which helps users who type "git checkout <branch>" by mistake, when they really wanted to do "git checkout -t <remote>/<branch>". I am certain that most new users who make this mistake will not understand what's going on, even if they read the output.

I believe that it's because of things like this that many users still consider git to be complicated and hard to use. That's what really bothers me.

And it makes me sad that you think it silly to even talk about it. Even if the feature does not end up getting removed I still hope that we will exercise more caution in the future and try to solve the real problem--which appears to be remote branch handling--rather than introducing more strange behavior.

Regards, Clemens

Previous: Miles BaderNext: Matthieu Moy
Message 20 of 34 in “DWIM "git checkout frotz" to "git checkout -b frotz origin/frotz"”
  1. Clemens BuchacherJun 5, 2010
  2. Sverre RabbelierJun 5, 2010
  3. Clemens BuchacherJun 5, 2010
  4. Sverre RabbelierJun 5, 2010
  5. Clemens BuchacherJun 5, 2010
  6. Nicolas PitreJun 5, 2010
  7. Jeff KingJun 6, 2010
  8. Clemens BuchacherJun 6, 2010
  9. Jacob HelwigJun 6, 2010
  10. Clemens BuchacherJun 6, 2010
  11. Sverre RabbelierJun 6, 2010
  12. Jacob HelwigJun 6, 2010
  13. Clemens BuchacherJun 7, 2010
  14. Jan KrügerJun 7, 2010
  15. Clemens BuchacherJun 7, 2010
  16. Johan HerlandJun 6, 2010
  17. Matthieu MoyJun 6, 2010
  18. Clemens BuchacherJun 6, 2010
  19. Miles BaderJun 7, 2010
  20. Clemens BuchacherJun 7, 2010
  21. Matthieu MoyJun 7, 2010
  22. Clemens BuchacherJun 7, 2010
  23. Bruce StephensJun 7, 2010
  24. Michael J GruberJun 8, 2010
  25. demerphqJun 8, 2010
  26. Michael J GruberJun 8, 2010
  27. Miles BaderJun 8, 2010
  28. Clemens BuchacherJun 8, 2010
  29. demerphqJun 8, 2010
  30. Matthieu MoyJun 8, 2010
  31. Miles BaderJun 8, 2010
  32. Jeff KingJun 8, 2010
  33. Clemens BuchacherJun 8, 2010
  34. Paolo BonziniJun 7, 2010

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.