I've just started taking a closer look at vcsh for keeping my
dot-files in git.  Currently I'm keeping them all in a single git
repo, which I check out straight into my $HOME (i.e. I have a
$HOME/.git).  I think I like the approach of vcsh better, but there is
one little detail that I can't seem to work out: how can I control
where submodules are recorded?

I have a few submodules in my $HOME for the solarized colour scheme:

[submodule ".solarized/gnome-terminal-colors-solarized"]
        path = .solarized/gnome-terminal-colors-solarized
        url = https://github.com/sigurdga/gnome-terminal-colors-solarized.git
[submodule ".solarized/ls-colors-solarized"]
        path = .solarized/ls-colors-solarized
        url = https://github.com/sigurdga/ls-colors-solarized.git
[submodule ".solarized/mutt-colors-solarized"]
        path = .solarized/mutt-colors-solarized
        url = https://github.com/altercation/mutt-colors-solarized.git

I would like to record them in separate vcsh-repos, so that the colour
schemes are kept in the most obvious repo, e.g. the mutt colour scheme
is a submodule of ~/.config/vcsh/repo.d/mutt.git.  But I can't find
any way to tell `git submodule` where to record the information, it
always uses $GIT_WORK_TREE/.gitmodules.  Is there something I've
missed here?


I am aware I could just skip using submodules, just clone them, and
then use something like `mr` to keep them up-to-date.  The only limit
is I'd like to be able to use it in cygwin too.

Magnus Therning                      OpenPGP: 0xAB4DFBA4 
email: mag...@therning.org   jabber: mag...@therning.org
twitter: magthe               http://therning.org/magnus

In a hierarchy, every employee tends to rise to his level of incompetence.
     -- The Peter Principle

Attachment: pgp_HyMdNWmEk.pgp
Description: PGP signature

Reply via email to