On Mi, 21 Aug 2019, Bram Moolenaar wrote:
> > On Mi, 21 Aug 2019, Christian Brabandt wrote: > > Alternatively, we could also enable the mercurial repository at OSDN > > It would be nice if that works. So far OSDN has been reliable and > responsive to any problems. Okay, I also setup osdn mercurial. https://osdn.net/projects/vim/scm/hg/vim/ I would call it experimental. Just in case you want to update your scripts to also push directly to the OSDN repository. Then we probably need to set it up a bit differently. Let me know if you want to do that. > Not sure what happens win 256bit.org when you are on holiday :-). The server doesn't actually care if I am on holiday ;) Well in case the server has some problems, several other things would break: - the github notification forwarding - the mercurial mirror wouldn't updated (bitbucket and now also hg.256bit.org and osdn) - the vim-win32-installer repository wouldn't be updated - coverity reports wouldn't be generated (that was a bit flaky in the last time, I hope to have resolved that) Best, Christian -- Man soll keine Dummheit zweimal begehen, die Auswahl ist schließlich groß genug. -- Jean-Paul Sartre -- -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/20190821132203.GD10736%40256bit.org.
