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:
Priority: optional
Build-Depends: debhelper (>= 5), dpkg-dev (>= 1.9.0)
Maintainer: Joey Hess <joeyh@debian.org>
Priority: optional
Build-Depends: debhelper (>= 5), dpkg-dev (>= 1.9.0)
Maintainer: Joey Hess <joeyh@debian.org>
-Standards-Version: 3.7.2
+Standards-Version: 3.7.3
Homepage: http://kitenet.net/~joey/code/mr/
Vcs-Git: git://git.kitenet.net/mr
Homepage: http://kitenet.net/~joey/code/mr/
Vcs-Git: git://git.kitenet.net/mr
Architecture: all
Section: utils
Depends:
Architecture: all
Section: utils
Depends:
-Suggests: subversion, git-core, cvs, bzr
+Suggests: subversion, git-core, cvs, bzr, mercurial, darcs
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
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, and bzr repositories,
- and support for other revision control systems can easily be added.
+ supports any combination of subversion, git, cvs, mecurial,
+ bzr and darcs repositories, and support for other revision control systems
+ can easily be added.
.
It is extremely configurable via simple shell scripting. Some examples
.
It is extremely configurable via simple shell scripting. Some examples
- of things it can be configured to do include:
+ of things it can 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.
.
* 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.
+ * Run several repository updates in parallel, greatly speeding up
+ the update process.