On Wednesday, August 19, 2015 at 9:03:52 AM UTC-4, Olaf wrote: > On 19-Aug-15, Bram Moolenaar wrote: > > > > Justin M. Keyes wrote: ... > > > 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
How many URLs referring to the old tags are out there and how crucial is it to keep them working? And is there any point trying to do so if code.google.com is going to be shut down anyway? As far as I understand the tags have been changed to confirm to a more conventional format. The move to GitHub is a good opportunity for such a change. > > > 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. VCS tags are just symbolic names that refer to a particular commit. Unlike mercurial, git does not store them in a versioned repository file (.hgtags in Mercurial) so the tags in git can be added, removed or renamed anytime without affecting the repository commit hashes at all. For a consistency and simplicity sake, I would vote for using only the new format and not having multiple tags per commit. Pavol -- -- 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.
