* Pierre Habouzit <madcoder@xxxxxxxxxx> wrote: > > for example, if i type "git-checkout" in a Linux kernel tree, it > > just sits there for up to a minute, and "does nothing". That is > > totally wrong, human-interaction wise. Then after a minute it just > > returns. What happened? Why? Where? A newbie would then try > > "git-checkout -v", using the well-established "verbose" flag, but > > that gives: > > > > Usage: /usr/bin/git-checkout [-q] [-f] [-b <new_branch>] [-m] [<branch>] [<paths>...] > > not anymore: > > $ git checkout -v > error: unknown switch `v' > usage: git-branch [options] [<branch>] [<paths>...] > > -b ... create a new branch started at <branch> > -l create the new branchs reflog > --track tells if the new branch should track the remote branch > -f proceed even if the index or working tree is not HEAD > -m performa three-way merge on local modifications if needed > -q, --quiet be quiet > > Not all commands are migrated to this new scheme though. > > The next git has a _lot_ of things done better wrt UI and such issues. > Though some backward incompatible changes must be introduced with the > proper deprecation warnings, so that people can adapt. hey, cool! Just when i decide to complain about it, after 2 years of suffering, it's already fixed in the devel branch =;-) I'll post suggestions once i have tried out the next version. I'm happy that the git "first impression" that new users are getting (and the many pitfalls that they can fall into) is being actively reviewed and improved. It's i think the main barrier for git world dominance :-) Ingo - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
