]> git.madduck.net Git - code/myrepos.git/blob - README

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:

update
[code/myrepos.git] / README
1 You have a lot of version control repositories. Sometimes you want to
2 update them all at once. Or push out all your local changes. You use
3 special command lines in some repositories to implement specific workflows.
4 Myrepos provides a `mr` command, which is a tool to manage all your version
5 control repositories.
6
7 It supports git, svn, mercurial, bzr, darcs, cvs, fossil and veracity.
8
9 Author: Joey Hess
10 Homepage: http://myrepos.branchable.com/
11
12 The mr command is intended to be very self-contained, since it might be
13 useful to check it into ~/bin when keeping your home in version control. It
14 has no dependencies aside from basic perl. (The included webcheckout
15 command has more dependencies, specifically the LWP::Simple and
16 HTML::Parser CPAN modules, and optionally the URI module.)
17
18 To install mr, just copy mr into your PATH somewhere.
19
20 To get started using mr, perhaps you already have some checked out
21 repositories. Go into each one and run "mr register". Now mr has
22 a list of them in ~/.mrconfig, which you can edit later to tune its
23 operation.
24
25 Suppose you've cd'd to ~/src, and it has many repositories under it.
26 To update them all, run "mr update". To commit any pending changes in
27 each, run "mr commit". To check the status of each, you could run
28 "mr status".
29
30 For further details, and lots of configuration options, see the mr(1) man
31 page or the website, http://myrepos.branchable.com/