]> git.madduck.net Git - code/myrepos.git/commitdiff

madduck's git repository

Every one of the projects in this repository is available at the canonical URL git://git.madduck.net/madduck/pub/<projectpath> — see each project's metadata for the exact URL.

All patches and comments are welcome. Please squash your changes to logical commits before using git-format-patch and git-send-email to patches@git.madduck.net. If you'd read over the Git project's submission guidelines and adhered to them, I'd be especially grateful.

SSH access, as well as push access can be individually arranged.

If you use my repositories frequently, consider adding the following snippet to ~/.gitconfig and using the third clone URL listed for each project:

[url "git://git.madduck.net/madduck/"]
  insteadOf = madduck:

improve description
authorJoey Hess <joey@kodama.kitenet.net>
Sun, 14 Oct 2007 06:00:50 +0000 (02:00 -0400)
committerJoey Hess <joey@kodama.kitenet.net>
Sun, 14 Oct 2007 06:00:50 +0000 (02:00 -0400)
debian/control
mr

index 075a28385c8c07a984f87fb59f1b46ca2c29a1bd..740bfbc9203044c42452d3981da77a4238b5eeb2 100644 (file)
@@ -13,9 +13,15 @@ Section: utils
 Depends: 
 Suggests: subversion, git-core, cvs, bzr
 Description: a Multiple Repository management tool
 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.
diff --git a/mr b/mr
index 83b595221886af7b802cecc888aedc2aab1f11ce..3cc603f6c3fba08a3007afc2e8139c63238a74a3 100755 (executable)
--- a/mr
+++ b/mr
@@ -26,13 +26,11 @@ B<mr> [options] action [params ...]
 
 =head1 DESCRIPTION
 
 
 =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
 
 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