Hi, On Sun, 21 Oct 2007, Andreas Ericsson wrote: > Johannes Schindelin wrote: > > > On Sun, 21 Oct 2007, Jakub Narebski wrote: > > > > > On 10/20/07, Steffen Prohaska <prohaska@xxxxxx> wrote: > > > > > > > Maybe we could group commands into more categories? > > > > > > > > plumbing: should be hidden from the 'normal' user. Porcelain > > > > should be sufficient for every standard task. > > > > > > The problem is division between what is porcelain and what is > > > plumbing. Some commands are right on border (git-fsck, > > > git-update-index, git-rev-parse comes to mind). > > > > Sorry, but my impression from the latest mails was that the commands > > are fine. What is lacking is a nice, _small_ collection of > > recommended workflows. And when we have agreed on such a set of > > workflows, we optimize the hell out of them. Only this time it is not > > performance, but user-friendliness. > > http://www.kernel.org/pub/software/scm/git/docs/everyday.html would be a > good starting point, I think. I don't think so. Way too few authors were involved in writing this document, so it is not "typical" in and of itself. I'd really like people to respond not so much with broad and general statements to my mail (those statements tend to be rather useless to find how to make git more suitable to newbies), but rather with concrete top ten lists of what they do daily. My top ten list: - git diff - git commit - git status - git fetch - git rebase - git pull - git cherry-pick - git bisect - git push - git add Of course, my list is somewhat skewed (because I am quite comfortable with the commands git provided; otherwise I would have provided -- unlike others, probably -- patches, and would have fought -- also unlike others -- to get them in, such as --color-words). So again, I'd like people who did _not_ tweak git to their likings to tell the most common steps they do. My hope is that we see things that are good practices, but could use an easier user interface. Ciao, Dscho - 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
