I have browsed through Git documentation: "A tutorial introduction to git" (tutorial.txt), "A short git tutorial" (core-tutorial.txt) which contrary to the title is the tutorial in low-level git commands and is longer that the first one, "Everyday GIT With 20 Commands Or So" (everyday.txt) and "git for CVS users" (cvs-migration.txt) which does not mention git-blame and git-annotate. What I miss is walkthrough type tutorial, describing typical workflow (or workflows), and tutorial concentrating on advanced topics which may come once in a while or for some topics only, but it would be nice to know how to resolve them. Perhaps some of the following problems would need Git improvement (e.g. better support for subprojects: "bind" idea)... 1. Description of typical workflow, with 'stable'/'maintenance'/'fixes' and 'development'/'master'/'main' branches, how to put bugfixes into both branches etc. Perhaps description of git branches and workflow, or Linux kernel branches and workflow. 2. Contrib: how to add project which was externally managed to contrib and later/or to core, preserving history. Examples: gitk for git, or like perhaps parsecvs would be for git, or like git-svn for git. 3. Subprojects: how to manage project which depends on other externally managed (third-party) project, and perhaps needs patches for it. Examples: out of tree kernel patches + userspace tools, plugin for some program which may need bugfixes, program which need some library, gitk before incorporating into git,... Perhaps description of the whole sequence of project development from add-on project (some new filesystem for Linux, gitk) to being incorporated into bigger project (filesystem included in Linux kernel, gitk in git repository). 4. Splitting repository: splitting one big project (X.org, Linux distribution) into modules. -- Jakub Narebski Warsaw, Poland - : 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