Gitslave http://gitslave.sf.net creates a group of related repositoriesâ??a superproject repository and a number of slave repositoriesâ??all of which are concurrently developed on and on which all git operations should normally operate; so when you branch, each repository in the project is branched in turn. Similarly when you commit, push, pull, merge, tag, checkout, status, log, etc; each git command will run on the superproject and all slave repositories in turn. This sort of activity may be very familiar to CVS and (to a lesser extent) Subversion users. Gitslave's design is for simplicity for normal git operations. Gitslave is an alternative to git-submodules: easier to use and better for some (but not all) workflows. When you have a problem which calls for easy multirepository management without lots of synchronization, where you typically might want to run the same git command over every repository in your project, gitslave is the solution for you. Release note highlights since last announcement, see release notes at http://gitslave.sf.net for more details. ---------------------------------------------------------------------- * Now supports git+ssh:// and host:repo style GRLs Traditionally gitslave has only supported /path/to/repo and URL (ssh://host/path/to/repo) style Git Resource Locators. Gitslave has now been taught about the alternate reference styles. * gits now has pager support gits will use less, $PAGER, and $GIT_PAGER hopefully similar to how native git uses pagers for output. * gits will not clean directories with .git in them Replicating recent git functionality, `gits clean -dfx` will not destroy repositories. This helps the situation where different branches have different slave modules attached. * Recursive subprojects With the use of `gits attach --recursive=.gitslave URL DIRECTORY` gitslave now fully support recursive subprojects (or slaves which are themselves gitslave masters of yet more slaves). * gitslave tutorial created A tutorial was created which walks the reader through a from-scratch repository creation using the most popular and needed git commands in the multi-repository gitslave environment. The tutorial and overall gitslave website is now stored as part of gitslave. * gits pulls more efficient and safer. Gits pulls perform a pull on all available local branches. This now should perform only one fetch (in most cases). Also --rebase is safer by using --preserve-merges (in most cases). * gits now implements paginated output by default, just like git Pagination is only enabled if standard output is a tty (and there is a controlling tty for the pager to take input from). If you do not want paginated output, the -n or --no-pager option disables it. All the git pager configuration settings (GIT_PAGER and PAGER environment variables, and core.pager configuration setting) are honored. * gits populate can now request population of specific ifpresent modules * gits clone now supported for easy project cloning * gits detach now supported for easier project maintenance ---------------------------------------------------------------------- -Seth Robertson -- 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