The "official" solution, if the Mercurial server is retired forever,
is to use git instead, but to at least one of us (me) and possibly
more, git is so foreign that we would rather explore all other
possible solutions before resorting to it. This message is written by
and for this kind of user.
Solution 1 : Remain with the last Vim executables we compiled from the
supposedly defunct Mercurial sources.
-- This seems to be a valid stopgap measure as long as other measures
(see below) provide no higher patchlevel of Vim ; but it is not usable
forever.
Solution 2 : Get our Vim executables elsewhere, for instance from a
Linux distribution or from a precompiled MacVim or Vim-for-Windows
distribution.
-- These executables are never the latest of the newest, and they are
almost never configured according to the set of features we would have
chosen if we had configured and compiled our own Vim executables, so
if we do that we will forever regret that we can't configure our own
Vim anymore : we will forever feel like second-rank citizens compared
to what we used to be. So it is a valid solution but never fully
satisfying.
Solution 3 : Enable the "gif" extension in Mercurial, learn how to use
it, and use it to make the official git repository appear like a
Mercurial repository from where we sit.
-- The problem here is "learn how to use it" : indeed, the online
Mercurial help about the git extension is practically nil : here it is
:
hg config extensions.git= help git
git extension - grant Mercurial the ability to operate on Git
repositories. (EXPERIMENTAL)
This is currently super experimental. It probably will consume
your firstborn a la Rumpelstiltskin, etc.
no commands defined
That's all. (I've added indentation to separate the lines of output
even if linebreaks are added in e-mail transit.) To me, such a
so-called "help" is actually no help at all, so I admire Christian all
the more for having succeeded to actually bring a working git-to-hg
server up and running, even if it is now defunct, and I hope it isn't.
If I am to someday understand how to use Mercurial on a git server
(and make no mistake : I hope I someday will) I think I will have to
meekly and politely ask Christian to write a "real" HowTo page that
could at least compare with, if not necessarily attain the level of
excellence of, what we have become accustomed to by perusing the Vim
help. I know this is a tall order, and I don't know if Christian will
have the time and staying power to provide such a HowTo to make others
benefit from his experiences ; but AFAICT that's the only exit I see
from this apparently dead-end situation, and I don't like it.
Solution 4 : Convince Christian (or someone) to move the Mercurial
server to some place where it will be available again, with all the
desired throughput.
-- The problem with this is that it is not in everyone's hands : my
ISP has (some years ago already) shut down all the access I had to a
user website, so even if I had the necessary knowledge to set up a
public git-to-Mercurial server (which I alas don't), I don't have the
means. I can of course argue in favour of such a solution, but I
cannot "put my hands where my mouth is" otherwise I would already have
started doing it. Christian obviously has the necessary knowledge ;
maybe someone else has it too ; I don't. Please anyone, if you have
both the knowledge and the means, please consider setting up a
Mercurial server somewhere accessible, so for the rest of us it will
just be a matter of adjusting the source aliases in our Mercurial
client's per-repository configuration for Vim, which is easy as a
breeze.
Best regards,
Tony.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/vim_dev/CAJkCKXuYWmt3ZyabLXT4c-pV2W8mkGRRQVtRjuU7rUYPO5K-EQ%40mail.gmail.com.
