Dealing with .gitmodules

martin f krafft madduck at
Fri Mar 31 07:56:59 CEST 2017

also sprach Joshua Haase <hahj87 at> [2017-03-31 05:37 +0200]:
> > The file .gitmodules (man 5 gitmodules, for use with git-submodule)
> > is hardcoded to reside in $GIT_WORK_DIR/.gitmodules. As vcsh
> > repositories all share the same work dir, there's a conflict.
> Why do you need git modules?

For instance, my awesome config relies on the lain plugin, and
I also use subprojects for e.g. pass, mutt, vim, and others.

How else would you do it? Note that I consider a checkout as part of
a configuration, so I want to decide myself when I pull a new
version and commit that to config, along with possibly required
changes therein. Thus, using myrepos to just recursively pull
doesn't really do what I expect. git-submodules is exactly what
I want.

@martinkrafft | |
"i can stand brute force, but brute reason is quite unbearable. there
 is something unfair about its use. it is hitting below the
                                                      -- oscar wilde
spamtraps: madduck.bogus at
-------------- next part --------------
A non-text attachment was scrubbed...
Name: digital_signature_gpg.asc
Type: application/pgp-signature
Size: 1118 bytes
Desc: Digital GPG signature (see
URL: <>

More information about the vcs-home mailing list