Am Mittwoch, 19. August 2015, 19:00:36 schrieb Justin M. Keyes: > On Aug 19, 2015 5:57 PM, "Markus Heidelberg" <[email protected]> > wrote: > > > > 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. > > It will be read-only, will it not? That was the purpose of the "deep > linking" talk, i thought. Old URLs (say, in a repository which will _not_ > rewrite its history) will continue to point to the patches instead of being > broken.
http://google-opensource.blogspot.de/2015/03/farewell-to-google-code.html * August 24, 2015 - The site goes read-only. You can still checkout/view project source, issues, and wikis. * January 25, 2016 - The project hosting service is closed. You will be able to download a tarball of project source, issues, and wikis. These tarballs will be available throughout the rest of 2016. What exactly will be deep-linked, seems to be unclear. I don't think this feature is important, though. > > Furthermore, nobody should use the Google repository anymore from now > > on, it is outdated with the next patches. > > Er, right, except for old URLs referencing those patches, originating from > sources that cannot be updated. Which will stop working in 5 months. It's just that they stop working earlier now. Broken URLs are not a new phenomenon in the internet. But I don't really care. If the old tags should exist in the Google repository, I won't have a problem with it, unless they appear in the new Git repo. -- -- 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.
