On Wed, Nov 20, 2024 at 2:10 AM Tony Mechelynck
<antoine.mechelynck@gmail.com> wrote:
>
> On Tue, Nov 19, 2024 at 4:47 PM Christian Brabandt <cblists@256bit.org> wrote:
> >
> > Hi,
> > just to let everybody know. Because of serious load issues, the HG
> > bridge is disabled for now.
> >
> > Just for my reference, how many users are still using it hg.256bit.org?
>
> I don't know how many are, but as I suppose you already know, I am one
> of them. For some reason Mercurial feels congenial to me and git
> doesn't.
>
> My current Mercurial configuration includes the following remote
> repository aliases, which I am listing alphabetically below with name,
> URL, and current response to "hg in". Some of them may be obsolete.
> bitbucket = https://bitbucket.org/vim-mirror/vim
> Not found.
> default = http://hg.256bit.org/vim
> Not found.
> osdn = https://hg.osdn.net/view/vim/vim
> Certificate has expired.
> In other words, the latter one is still responding, but rejecting the
> request for lack of an up-to-date certificate.
> I practically always pull from the "default" source unless, like now,
> it really goes down.
P.S. I also install the vim executable from openSUSE Tumbleweed
(currently at version/patchlevel 9.1.836, and not with the same
+features as the Vim which I compile myself, or (if Mercurial
distribution never resumes) which I used to (currently at
version/patchlevel 9.1.873). This openSUSE vim is at /bin/vim and at
/user/bin/vim while mine is at /usr/local/bin/vim which is earlier in
the $PATH. Similarly for gvim, view, gview, etc. symlinks.
>
> > If there are very many users, we should probably move it to the vim.org
> > domain.
>
> If you could do that without too much hassle, for someone at the
> receiving end like me it would just be a matter of adjusting the
> source aliases (i.e. those displayed by "hg paths") to make sure that
> the "default" source is the one we normally want to pull from. A piece
> of cake.
>
> >
> > Thanks,
> > Chris
>
> My pleasure,
> Tony.
> >
> > On Tue, 19 Nov 2024, Tony Mechelynck wrote:
> >
> > > On Tue, Nov 19, 2024 at 2:55 PM Christian Brabandt <cblists@256bit.org> wrote:
> > > >
> > > >
> > > > On Tue, 19 Nov 2024, Tony Mechelynck wrote:
> > > >
> > > > > linux-tuxedo:~/.build/vim/vim-hg # hg in || echo 'exit status' $? ; date
> > > > > abort: error: Connection refused
> > > > > exit status 255
> > > > > Tue 19 Nov 14:48:32 CET 2024
> > > > > linux-tuxedo:~/.build/vim/vim-hg # hg in || echo 'exit status' $? ; date
> > > > > abort: error: Connection refused
> > > > > exit status 255
> > > > > Tue 19 Nov 14:48:50 CET 2024
> > > > >
> > > > > Let us hope this is only temporary.
> > > >
> > > > It was. Sometimes there is a bit of load on the server (for unknown
> > > > reasons).
> > > >
> > > > Thanks,
> > > > Christian
> >
> > Mit freundlichen Grüßen
> > Christian
> > --
> > YOW!! Now I understand advanced MICROBIOLOGY and th' new TAX REFORM laws!!
> >
> > --
> > --
> > 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+unsubscribe@googlegroups.com.
> > To view this discussion visit https://groups.google.com/d/msgid/vim_dev/Zzyy/lTDSAwYqiH/%40256bit.org.
--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/CAJkCKXsJ1NUT6y9YkU%2Brq86yfw28ZrPqaLmZtmuVD%3DJ9grKU6Q%40mail.gmail.com.
No comments:
Post a Comment