]> git.madduck.net Git - code/myrepos.git/blob - 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:

9a1a8955819ad1fd57ac1a3947be33e4a1c5367e
[code/myrepos.git] / debian / control
1 Source: mr
2 Section: utils
3 Priority: optional
4 Build-Depends: debhelper (>= 7), dpkg-dev (>= 1.9.0)
5 Maintainer: Joey Hess <joeyh@debian.org>
6 Standards-Version: 3.8.0
7 Homepage: http://kitenet.net/~joey/code/mr/
8 Vcs-Git: git://git.kitenet.net/mr
9
10 Package: mr
11 Architecture: all
12 Section: utils
13 Depends: 
14 Suggests: subversion, git-core, cvs, bzr, mercurial, darcs
15 Description: a Multiple Repository management tool
16  The mr(1) command can checkout, update, or perform other actions on
17  a set of repositories as if they were one combined respository. It
18  supports any combination of subversion, git, cvs, mecurial,
19  bzr, and darcs repositories, and support for other revision control
20  systems can easily be added. (There are extensions adding support for
21  unison and git-svn.)
22  .
23  It is extremely configurable via simple shell scripting. Some examples
24  of things it can do include:
25  .
26   * Update a repository no more frequently than once every twelve hours.
27   * Run an arbitrary command before committing to a repository.
28   * When updating a git repository, pull from two different upstreams
29     and merge the two together.
30   * Run several repository updates in parallel, greatly speeding up
31     the update process.
32   * Remember actions that failed due to a laptop being offline, so they
33     can be retried when it comes back online.