git submodules in ~ (was: Introductory git article?)
martin f krafft
madduck at madduck.net
Wed Feb 20 11:12:58 CET 2008
also sprach Jens Peter Secher <jpsecher at diku.dk> [2008.02.17.1252 +0100]:
> I tried various systems, but ended up only moving (and linking)
> private dotfiles like .ssh/ and .gnupg/ in a git submodule. That
> way I can check out my homedir without the private stuff on an
> insecure machine, as others have described.
The way submodules work is that the parent has a reference to
a specific revision of a submodule. So if you have two machines and
each have a submodule in ~/foo at commit A and you add some commits
to the first ~/foo submodule and push them, you cannot just tell
your ~ on the other machine to update; instead, you have to pull
~/foo and then commit ~ to tell it about the updated submodule.
I personally prefer the mr tool to submodules for this task.
martin | http://madduck.net/ | http://two.sentenc.es/
"never attribute to malice what can be
adequately explained by incompetence."
-- mark twain
spamtraps: madduck.bogus at madduck.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Digital signature (see http://martin-krafft.net/gpg/)
More information about the vcs-home