Depends:
Suggests: subversion, git-core, cvs, bzr
Description: a Multiple Repository management tool
- The mr(1) command allows you to register a set of repositories in
- a .mrconfig file, and then checkout, update, or perform other actions on
- the repositories as if they were one big respository.
+ The mr(1) command can checkout, update, or perform other actions on
+ a set of repositories as if they were one combined respository. It
+ supports any combination of subversion, git, cvs, and bzr repositories,
+ and support for other revision control systems can easily be added.
.
- Any mix of revision control systems can be used with mr(1), and you can
- define arbitrary actions for commands like "update", "checkout", or "commit".
+ It is extremely configurable via simple shell scripting. Some examples
+ of things it can be configured to do include:
+ .
+ * Update a repository no more frequently than once every twelve hours.
+ * Run an arbitrary command before committing to a repository.
+ * When updating a git repository, pull from two different upstreams
+ and merge the two together.
=head1 DESCRIPTION
-B<mr> is a Multiple Repository management tool. It allows you to register a
-set of repositories in a .mrconfig file, and then checkout, update, or
-perform other actions on the repositories as if they were one big
-respository.
-
-Any mix of revision control systems can be used with B<mr>, and you can
-define arbitrary actions for commands like "update", "checkout", or "commit".
+B<mr> is a Multiple Repository management tool. It
+can checkout, update, or perform other actions on
+a set of repositories as if they were one combined respository. It
+supports any combination of subversion, git, cvs, and bzr repositories,
+and support for other revision control systems can easily be added.
B<mr> cds into and operates on all registered repsitories at or below your
working directory. Or, if you are in a subdirectory of a repository that