Hi Bram!

On Fr, 14 Aug 2015, Bram Moolenaar wrote:

> 
> Christian Brabandt wrote:
> 
> > On Do, 13 Aug 2015, Bram Moolenaar wrote:
> > 
> > > Then, I want to check in a change to Google code only, that produces an
> > > error when trying to build that version.  This is because there is no
> > > way to stop the Mercurial repository from serving, users who simply pull
> > > there won't notice anything wrong (except not getting any more updates).
> > > So you would need to halt your update script before that happens, and
> > > sync from github.  This *should* have the same version history then.
> > 
> > I already sync from github ;)
> > 
> > But if you check in an error to google code, that means, users won't be 
> > able to just switch the repository URL, because a commit would be 
> > missing? Can't we just keep the Google Code repository alone? It will be 
> > closed in January anyhow, so users should notice 4 month later when the 
> > urls won't work anymore.
> 
> If it works better to have a linear sequence, we could checkin the
> change to Google code, and then in the new repository revert it.

Yes, that's what I am going to do. I will sync the broken commit and 
then revert it. After that the sync from the github repository should 
work.

> The only problem with this is that there won't be a grace period, the
> moment I do this everybody is forced to switch over.  Hmm, unless I
> delay pushing this change to Mercurial, which means I have to keep this
> locally when converting to git.  That would work.

Just tell me, when you are going to do this. I will then reclone and 
setup everything afterwards. I need some time, in the evening next week 
would be good.

> Problem with waiting is that users have no clue whatsoever why they are
> not getting updates.  Someone reading outdated instructions may think
> this is still the official repository.

Speaking of which, http://www.vim.org/develop.php
needs to be adjusted.

At the very least the new repository should be added

But better would be to have a version, that explains how to work with 
git.

And how to handle runtime patches should be explained as well.

Best,
Christian
-- 
Anfrage an Radio Eriwan:
"Wäre es möglich, daß man anstelle von J.F. Kennedy Nikita Chrustschow
erschossen hätte?"
Antwort: "Im Prinzip ja, aber es ist fraglich, ob Onassis die Witwe
genommen hätte." 

-- 
-- 
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].
For more options, visit https://groups.google.com/d/optout.

Raspunde prin e-mail lui