]> 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:

typo
[code/myrepos.git] / debian / control
index 7f21b19474925b9309b4e649c748ad3860869968..9a1a8955819ad1fd57ac1a3947be33e4a1c5367e 100644 (file)
@@ -1,9 +1,9 @@
 Source: mr
 Section: utils
 Priority: optional
-Build-Depends: debhelper (>= 5), dpkg-dev (>= 1.9.0)
+Build-Depends: debhelper (>= 7), dpkg-dev (>= 1.9.0)
 Maintainer: Joey Hess <joeyh@debian.org>
-Standards-Version: 3.7.2
+Standards-Version: 3.8.0
 Homepage: http://kitenet.net/~joey/code/mr/
 Vcs-Git: git://git.kitenet.net/mr
 
@@ -16,8 +16,9 @@ Description: a Multiple Repository management tool
  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, mecurial,
- bzr and darcs repositories, and support for other revision control systems
- can easily be added.
+ bzr, and darcs repositories, and support for other revision control
+ systems can easily be added. (There are extensions adding support for
+ unison and git-svn.)
  .
  It is extremely configurable via simple shell scripting. Some examples
  of things it can do include:
@@ -28,3 +29,5 @@ Description: a Multiple Repository management tool
     and merge the two together.
   * Run several repository updates in parallel, greatly speeding up
     the update process.
+  * Remember actions that failed due to a laptop being offline, so they
+    can be retried when it comes back online.