On Mon, Nov 26, 2018 at 5:01 PM Ævar Arnfjörð Bjarmason <avarab@xxxxxxxxx> wrote: > > So, what do you think? > > That "git checkout" does too many things is something that keeps coming > up in online discussions about Git's UI. Two things: > > a) It would really help to have some comparison of cases where these > split commands are much clearer or less ambiguous than > git-checkout. I can think of some (e.g. branch with the same name as > a file) but having some overall picture of what the new UI looks like > with solved / not solved cases would be nice. Also a comparison with > other SCMs people find less confusing (svn, hg, bzr, ...) Less ambiguous is indeed one of the reasons I wanted to do this. > b) I think we really need to have some end-game where we'd actually > switch away from "checkout" (which we could still auto-route to new > commands in perpetuity, but print a warning or error). Otherwise > we'll just end up with https://xkcd.com/927/ and more UI confusion > for all. I'm not going to remove "git checkout". Not until the majority of users are really in favor of the new ones. So my end-game plan is to just promote the two new commands in man pages, tutorial, advice... Perhaps at some point "git checkout" is also removed from "git help". But that's about it. If you want to stick with "git checkout", it's there (and not nagging you to move to new ones). -- Duy
