]> git.madduck.net Git - code/myrepos.git/blobdiff - debian/control

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:

projects / code / myrepos.git / blobdiff
? search:
summary | shortlog | log | commit | commitdiff | tree
raw | inline | side by side
incomplete work to try to guess the right mrconfig to register to
[code/myrepos.git] / debian / control
diff --git a/debian/control b/debian/control
index d125ef9e59cc643cf25731b175246418fbea2cf6..37323d53b851952f9eb12fa4e4798754ce05a339 100644 (file)
--- a/debian/control
+++ b/debian/control
@@ -11,11 +11,17 @@ Package: mr
 Architecture: all
 Section: utils
 Depends: 
-Suggests: subversion, git-core, cvs
+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.
hacking on myrepos

Legalese

All content available in this repository is copyright © martin f. krafft, unless otherwise noted.

All files and their content are released under the terms of the Artistic Licence 2.0, unless otherwise noted.

The operator of this repository shall not be held liable for offending content in pages linking to or linked from these page, nor does he endorse their content unless stated otherwise.