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

improve log message for checkouts
[code/myrepos.git] / debian / control
index d9b702c23ff89218bce1c78eb8591e0c0ea282e6..075a28385c8c07a984f87fb59f1b46ca2c29a1bd 100644 (file)
@@ -4,16 +4,18 @@ Priority: optional
 Build-Depends: debhelper (>= 5), dpkg-dev (>= 1.9.0)
 Maintainer: Joey Hess <joeyh@debian.org>
 Standards-Version: 3.7.2
 Build-Depends: debhelper (>= 5), dpkg-dev (>= 1.9.0)
 Maintainer: Joey Hess <joeyh@debian.org>
 Standards-Version: 3.7.2
+Homepage: http://kitenet.net/~joey/code/mr/
+Vcs-Git: git://git.kitenet.net/mr
 
 Package: mr
 Architecture: all
 Section: utils
 Depends: 
 
 Package: mr
 Architecture: all
 Section: utils
 Depends: 
-Suggests: subversion, git-core
+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
 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
all of the repositories at once.
the repositories as if they were one big respository.
  .
  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".
  .
  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".