Re: dependable submodules

From: Jens Lehmann <jens.lehmann@web.de>
Date: Mar 22, 2011, 18:56 UTC
Message-ID: <4D88F0DF.8080808@web.de>
In-Reply-To: <AANLkTinrvg=UkZJWCQt3hZXpAAgW=manhGPvk9s9KsCs@mail.gmail.com>

Am 22.03.2011 15:55, schrieb Daniel:

Show 12 quoted lines

> My current setup is that I'm simply versioning my home directory with
> mercurial. Some vim plugins are under git and since it's a different
> version control system I can check in the plugins easily. When I need
> to update those plugins, I just run git update, and check them into
> mercurial again. No problem, very easy.  I'm looking into what it
> would take to convert my repo to be completely git, and so far I have
> no exact way of dealing with those vim plugins since via submodules I
> have to rely on the external repos being present when I clone my
> homedir repo. Granted, if the repos have gone away a decade from now
> and my vim plugins are not present, it won't be the end of the world,
> but I want to see how close I can get to my current functionality when
> using git instead of mercurial.

You could add the .git directories of the vim plugin direcories that are under git to the .gitignore in your home directory. Then you can just continue to do what you are used to: Go into the vim plugin dir, run git update there, go back into your home directory and commit the new files and push everything to your remote. You'll lose the pointers from the vim plugin directories to their origins that way, but that doesn't seem to be a problem for you.