+\fBvcsh\fR \- Version Control System for $HOME \- multiple Git repositories in $HOME
...
...
@@ -70,7 +70,7 @@ Index: vcsh/vcsh.1
+\fBvcsh\fR run \fIrepo\fR \fIshell command\fR
+.
+.P
+\fBvcsh\fR status
+\fBvcsh\fR status [\fIrepo\fR]
+.
+.P
+\fBvcsh\fR upgrade \fIrepo\fR
...
...
@@ -132,6 +132,10 @@ Index: vcsh/vcsh.1
+If you need to clone a bundle of repositories, look into the \fBpost\-clone\-retired\fR hook\.
+.
+.TP
+commit
+Commit in all repositories
+.
+.TP
+delete
+Delete an existing repository\.
+.
...
...
@@ -180,7 +184,7 @@ Index: vcsh/vcsh.1
+.
+.TP
+status
+Show statuses of all vcsh repositories\.
+Show statuses of all/one vcsh repositories\.
+.
+.TP
+upgrade
...
...
@@ -248,6 +252,19 @@ Index: vcsh/vcsh.1
+.IP
+Defaults to \fIexact\fR\.
+.
+.TP
+\fI$VCSH_VCSH_WORKTREE\fR
+Can be \fIabsolute\fR, or \fIrelative\fR\.
+.
+.IP
+\fIabsolute\fR will set an absolute path; defaulting to \fI$HOME\fR\.
+.
+.IP
+\fIrelative\fR will set a path relative to \fI$GIT_DIR\fR\.
+.
+.IP
+Defaults to \fIabsolute\fR\.
+.
+.P
+Less interesting knobs you could turn:
+.
...
...
@@ -293,7 +310,7 @@ Index: vcsh/vcsh.1
+If you want to create hooks for a specific \fIvcsh\fR repository, simply prepend the repository\'s name, followed by a dot, i\.e\. <zsh\.pre\-run>\. Otherwise, the same rules as above apply\. The dot between the repository\'s name and the hook is mandatory, though\.
+.
+.P
+Available hooks are \fIpre\-enter\fR, \fIpost\-enter\fR, \fIpre\-run\fR, \fIpost\-run\fR, \fIpre\-upgrade\fR, and \fIpost\-upgrade\fR\. If you need more, vcsh is trivial to patch, but please let upstream know so we can ship them by default\.
+Available hooks are \fIpre\-clone\fR, \fIpost\-clone\fR, \fIpost\-clone\-retired\fR, \fIpre\-command\fR, \fIpost\-command\fR, \fIpre\-enter\fR, \fIpost\-enter\fR, \fIpre\-init\fR, \fIpost\-init\fR, \fIpre\-pull\fR, \fIpost\-pull\fR, \fIpre\-push\fR, \fIpost\-push\fR, \fIpre\-run\fR, \fIpost\-run\fR, \fIpre\-upgrade\fR, and \fIpost\-upgrade\fR\. If you need more, vcsh is trivial to patch, but please let upstream know so we can ship them by default\.
+.
+.SH "DETAILED HOWTO AND FURTHER READING"
+Manpages are often short and sometimes useless to glean best practices from\. While the author tried to avoid this in this case, manpages can not cover detailed howtos\.
...
...
@@ -329,7 +346,7 @@ Index: vcsh/vcsh.1
+This manpage and \fBvcsh\fR itself were written by Richard "RichiH" Hartmann\.
+.
+.SH "COPYRIGHT"
+Copyright 2011\-2013 Richard Hartmann \fIrichih\.mailinglist@gmail\.com\fR
+Copyright 2011\-2013 Richard Hartmann \fIrichih@debian\.org\fR