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.
1 vcsh(1) - manage and sync config files via git
2 ==============================================
6 `vcsh` clone <url> [<location>]
18 `vcsh` run <repo> <command>
20 `vcsh` seed-gitignore <repo>
24 `vcsh` <repo> <gitcommand>
29 `vcsh` allows you to have several `git`(1) repositories, all maintaining their
30 working trees in $HOME without clobbering each other. That, in turn, means you
31 can have one repository per config set (zsh, vim, ssh, etc), picking and
32 choosing which configs you want to use on which machine.
34 `vcsh` is using a technique called fake bare git repositories, keeping <$GIT_DIR>
35 in a different directory from <$GIT_WORK_TREE> which is pointed to <$HOME>.
37 The use of symlinks is not needed in this setup, making for a cleaner setup.
39 `vcsh` was designed with `mr`(1) in mind so you might want to install it alongside
40 vcsh. That being said, you can easily use `vcsh` without `mr` if you prefer.
42 A sample configuration for `vcsh` and `mr` can be found at
43 *https://github.com/RichiH/vcsh_mr_template*
48 Clone an existing repository.
51 Delete an existing repository.
54 Enter repository; spawn new <$SHELL>.
60 Initialize an empty repository.
63 List all local vcsh repositories.
66 Run command with <$GIT_DIR> and <$GIT_WORK_TREE> set. Allows you to run any
67 and all commands without any restrictions. Use with care.
70 Seed .gitignore.d/<repo> from git ls-files.
73 Set up repository with recommended settings.
75 * <repo> <gitcommand>:
76 Shortcut to run `vcsh` on a repo. Will prepend `git` to <command> by itself.
80 As noted earlier, `vcsh` will set <$GIT_DIR> and <$GIT_WORK_TREE> to the
81 appropriate values for fake bare git repositories.
83 ## SECURITY CONSIDERATIONS
85 `vcsh` allows you to execute arbitrary commands via `vcsh` run. For example,
86 speaking, adding a `sudo`(8) rule for `vcsh` would be pretty stupid.
90 None are known at this time, but reports and/or patches are more than welcome.
94 Like most people, the author initially made do with a single repository for all
95 config files, all of which were soft-linked into <$HOME>.
97 Martin F. Krafft aka madduck came up with the concept of fake bare git
100 vcsh was initally written by madduck. This version is a re-implementation from
101 scratch with a lot more features. madduck graciously agreed to let the author
106 This manpage and `vcsh` itself were written by Richard "RichiH" Hartmann.
110 Copyright 2011 Richard Hartmann <richih.mailinglist@gmail.com>
112 Licensed under the GNU GPL version 3 or higher.
114 https://github.com/RichiH/vcsh