On 16-Jan-2010 17:54, Markus Heidelberg wrote:
Ingo Karkat, 2010-01-10:
I would hope that the Mercurial repository will make it easier (i.e. no manual
import of sent patches, no separate Runtime sync) for Markus to update his Git
repo.
When the Mercurial repository becomes official and Vim finally has a
proper upstream, then vim_mainline.git becomes superfluous and that's
good.
I will stop updating it then and won't change it to import from the hg
repo.
I can understand your reasoning; after all, you've volunteered your resources to
update the Git repo, and the main pain point will then be gone. OTOH, I'm afraid
some Git users won't bother switching to Mercurial and will stop updating Vim
regularly.
unless and until that patch is adopted mainstream i'll be
sticking with git (unless markus stops maintaining it for some
reason)
vim_extended.git is based on vim_mainline so it will not be continued in
the same way. One solution would be to use a tool like hg-to-git to
import the official repo into a git branch, but I guess a better
approach would be to stay close to upstream and use a hg repo for
reduced trouble and increased compatibility. I haven't used hg except
for pulling and updating by now and I guess I don't like it as much as
git, but I think it would be the best solution.
That's sad to hear. I can only hope that someone will offer something like
vim_extended on Mercurial. Getting experimental patches to so many interested
users had never been so easy, it would be a real loss if this went away without
replacement.
Nonetheless, I'd like to say a big thank-you to you, Markus, for providing the
Git repositories! Through them, I got introduced to Git (and began to really
like it!)
-- regards, ingo
--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
