>> * git-branch is not verbose enough when creating a new >> branch, for a new user a little reassurance that what they >> meant to happen has happened would be nice. > > The same comment applies here. > > However, perhaps you could make lack of "[user] expert = true" > in ~/.gitconfig to trigger more verbose messages that say "yes > sir I did what I was told to do". > > Not interested in implementing that myself at all, though. > >> Tell them if they >> made a branch as well, which branch they are now on. > > I think you are talking about "checkout -b" not commit here; > this might be a borderline (branch creation is less often done > and it might warrant assuring feedback), but I think it still > falls into the "doing exactly what it was told to do" category. > Yes. checkout -b works. But only _if_ you have read the manpage. Someone thinking about branching at the current commit would just have git branch in mind (so would I). Its not obvious to say git checkout -b <newbranchname> oldbranch becouse checkout implies to advance to another version. -Peter - 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