On Thu, Jul 2, 2020 at 11:25 AM Christian Brabandt wrote:
>
>
> On Di, 20 Aug 2019, Tony Mechelynck wrote:
>
> > Full details:
> > https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket
> >
> > TLDR: Bit bucket won't allow creating *new* Mercurial repos starting
> > 2020-02-01 and o
Christian wrote:
> On Di, 20 Aug 2019, Tony Mechelynck wrote:
>
> > Full details:
> > https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket
> >
> > TLDR: Bit bucket won't allow creating *new* Mercurial repos starting
> > 2020-02-01 and on 2020-06-01 all existing Mercurial repos
On Di, 20 Aug 2019, Tony Mechelynck wrote:
> Full details:
> https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket
>
> TLDR: Bit bucket won't allow creating *new* Mercurial repos starting
> 2020-02-01 and on 2020-06-01 all existing Mercurial repos on bitbucket
> will be deleted.
On Fri, Aug 23, 2019 at 8:35 PM Bram Moolenaar wrote:
> Thanks, I updated https://www.vim.org/mercurial.php
> We'll update it again when we get feedback about which one works best.
I'm not sure there's a single one which works *best*, i.e. definitely
better than both others at the moment. AFAIK,
Christian wrote:
> On Do, 22 Aug 2019, Bram Moolenaar wrote:
>
> > What are the "hg clone" commands to use? For bitbucket it's:
> >
> > hg clone https://bitbucket.org/vim-mirror/vim
>
> hg clone http://hg.256bit.org/vim or
> hg clone https://hg.osdn.net/view/vim/vim
>
> For OSDN, the
On Fri, Aug 23, 2019 at 8:40 AM Christian Brabandt wrote:
>
>
> On Do, 22 Aug 2019, Bram Moolenaar wrote:
>
> > What are the "hg clone" commands to use? For bitbucket it's:
> >
> > hg clone https://bitbucket.org/vim-mirror/vim
>
> hg clone http://hg.256bit.org/vim or
> hg clone https://hg
On Do, 22 Aug 2019, Bram Moolenaar wrote:
> What are the "hg clone" commands to use? For bitbucket it's:
>
> hg clone https://bitbucket.org/vim-mirror/vim
hg clone http://hg.256bit.org/vim or
hg clone https://hg.osdn.net/view/vim/vim
For OSDN, the correct URL is also mentioned on the
Christian Brabandt wrote:
> On Do, 22 Aug 2019, Mike Williams wrote:
>
> > > That's what I did. Please try out: http://hg.256bit.org
> >
> > Works for me. Or would you prefer people to use the OSDN repo?
>
> All those repos are now synchronized, so from the git repo first the
> 256bit serve
On Do, 22 Aug 2019, Mike Williams wrote:
> > That's what I did. Please try out: http://hg.256bit.org
>
> Works for me. Or would you prefer people to use the OSDN repo?
All those repos are now synchronized, so from the git repo first the
256bit server repo is updated and from there it will be
On 21/08/2019 11:42, Christian Brabandt wrote:
> External Sender: Use caution with links/attachments.
>
> On Di, 20 Aug 2019, Mike Williams wrote:
>
>> Given the relatively low access it may be simpler to set up a small
>> hosted read-only server. The repo is only ~80MiB and most reads should
>>
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 mer
> On Mi, 21 Aug 2019, Christian Brabandt wrote:
>
> > On Di, 20 Aug 2019, Mike Williams wrote:
> >
> > > Given the relatively low access it may be simpler to set up a small
> > > hosted read-only server. The repo is only ~80MiB and most reads should
> > > be for delta updates.
> >
> > That's
On Mi, 21 Aug 2019, Christian Brabandt wrote:
>
> On Di, 20 Aug 2019, Mike Williams wrote:
>
> > Given the relatively low access it may be simpler to set up a small
> > hosted read-only server. The repo is only ~80MiB and most reads should
> > be for delta updates.
>
> That's what I did. P
On Di, 20 Aug 2019, Mike Williams wrote:
> Given the relatively low access it may be simpler to set up a small
> hosted read-only server. The repo is only ~80MiB and most reads should
> be for delta updates.
That's what I did. Please try out: http://hg.256bit.org
It should already mirror th
I'm also using mercurial to keep my vim up to date. But I could switch to git
though I really hate to do that.
--
--
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/mailli
The 2019-08-20 15:51, Christian Brabandt wrote:
> Does anybody know of other existing code sharing sites we could use instead?
What about sourcehut? Drew Devault has just made an announcement: "Sourcehut
welcomes Bitbucket refugees":
https://lists.sr.ht/~sircmpwn/sr.ht-announce/%3CBWEK6BW6V110.3A
The 2019-08-20 15:51, Christian Brabandt wrote:
> Does anybody know of other existing code sharing sites we could use instead?
What about sourcehut? Drew Devault has just made an announcement: "Sourcehut
welcomes Bitbucket refugees":
https://lists.sr.ht/~sircmpwn/sr.ht-announce/%3CBWEK6BW6V110.3A
On 20/08/2019 14:51, Christian Brabandt wrote:
> External Sender: Use caution with links/attachments.
>
> On Di, 20 Aug 2019, Tony Mechelynck wrote:
>
>> Full details:
>> https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket
>>
>> TLDR: Bit bucket won't allow creating *new* Mercur
On Tue, Aug 20, 2019 at 3:51 PM Christian Brabandt wrote:
>
>
> On Di, 20 Aug 2019, Tony Mechelynck wrote:
>
> > Full details:
> > https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket
> >
> > TLDR: Bit bucket won't allow creating *new* Mercurial repos starting
> > 2020-02-01 and o
On Di, 20 Aug 2019, Tony Mechelynck wrote:
> Full details:
> https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket
>
> TLDR: Bit bucket won't allow creating *new* Mercurial repos starting
> 2020-02-01 and on 2020-06-01 all existing Mercurial repos on bitbucket
> will be deleted.
Full details:
https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket
TLDR: Bit bucket won't allow creating *new* Mercurial repos starting
2020-02-01 and on 2020-06-01 all existing Mercurial repos on bitbucket
will be deleted. From then on it will only support git repos.
How it conc
21 matches
Mail list logo