Am Mittwoch, 19. August 2015, 15:03:38 schrieb Olaf Dabrunz: > On 19-Aug-15, Bram Moolenaar wrote: > > > > Justin M. Keyes wrote: > > > > > On 8/18/15, Bram Moolenaar <[email protected]> wrote: > > > > > > > > There were a couple of hiccups, but the repository has moved to GitHub > > > > now. It's in the destination place: https://github.com/vim/vim > > > > > > > > Now we need to do the git cleanup. I'll hold off until it looks OK, > > > > https://github.com/vim/vim-tryout is what it would look like. > > > > At least it doesn't have the old branches. Apparently the import > > > > resurrected what the Mercurial cleanup was supposed to remove. > > > > > > Why was the _mercurial_ tag format changed in the google code > > > repository? This breaks all URLs using the old tag format: > > > > > > https://code.google.com/p/vim/source/detail?r=v7-4-827 > > > > > > Now the URL must be formatted like this: > > > > > > https://code.google.com/p/vim/source/detail?r=v7.4.827 > > > > > > What is the purpose of VCS tags if they're going to be changed? It is > > > part of the VCS history. Only new tags should use the new format, not > > > the old tags.
In principle you are right, but it is different for this HG repository. AFAIR Bram would have removed the stale HG repository after the move to Git if it were possible, but it wasn't. Then the URLs immediately would not have been accessible anymore. Given that Google Code hosting will close in 5 months and thus the URLs will be broken anyway, I consider this change to be not very harmful at all. Furthermore, nobody should use the Google repository anymore from now on, it is outdated with the next patches. The intention was to have proper tag names (matching the version number) in the cleaned up Git repository. Since these should be identical in the new HG mirror, which also shouldn't contain a mess of two different tag naming schemes, the renaming has already been applied to the HG repo before conversion to Git. > > Yeah, it's not nice that old URLs stop working. Unfortunately you are > > too late with this remark, it already happened. We can't make both > > work, can we? > > Git allows multiple tags on a commit, and Mercurial seems to allow that > too (https://mercurial.selenic.com/wiki/Tag). Yes, it is possible with both systems. > Markus, does it work if your script only adds the new tag, keeping the > old one? The script has already been executed and the results pushed. Of course it would be possible to bring the old tags back with an additional commit, but as written above in my opinion this won't make much sense. Christian would have to revert the mess again in his mirror. -- -- 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.
