From: Jens Lehmann <Jens.Lehmann@web.de>
To: Daniel <daniel@netwalk.org>
Cc: in-gitvger@baka.org, Robert Pollak <robert.pollak@jku.at>,
git <git@vger.kernel.org>,
apenwarr@gmail.com
Subject: Re: dependable submodules
Date: Tue, 22 Mar 2011 19:56:31 +0100 [thread overview]
Message-ID: <4D88F0DF.8080808@web.de> (raw)
In-Reply-To: <AANLkTinrvg=UkZJWCQt3hZXpAAgW=manhGPvk9s9KsCs@mail.gmail.com>
Am 22.03.2011 15:55, schrieb Daniel:
> 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.
prev parent reply other threads:[~2011-03-22 18:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-20 0:53 dependable submodules Daniel
2011-03-20 4:27 ` Junio C Hamano
2011-03-20 4:32 ` Daniel
2011-03-20 12:36 ` Jens Lehmann
2011-03-20 16:06 ` Daniel
2011-03-21 16:18 ` Robert Pollak
2011-03-22 3:56 ` Daniel
2011-03-22 5:13 ` Avery Pennarun
2011-03-22 14:28 ` in-gitvger
2011-03-22 14:55 ` Daniel
2011-03-22 18:56 ` Jens Lehmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D88F0DF.8080808@web.de \
--to=jens.lehmann@web.de \
--cc=apenwarr@gmail.com \
--cc=daniel@netwalk.org \
--cc=git@vger.kernel.org \
--cc=in-gitvger@baka.org \
--cc=robert.pollak@jku.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).