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. > > 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?
Untested. Git allows multiple tags on a commit, and Mercurial seems to allow that too (https://mercurial.selenic.com/wiki/Tag). Markus, does it work if your script only adds the new tag, keeping the old one? Looking at hg-fast-export, it should have no problem picking up old and new tags. --- vim-hg-repo-cleanup-script.sh~ 2015-08-19 13:59:42.000000000 +0200 +++ vim-hg-repo-cleanup-script.sh 2015-08-19 14:00:48.000000000 +0200 @@ -164,7 +164,7 @@ for i in `hg tags --debug | tac | awk '/ REV=${i/*:/} OLDTAG=${i/:*/} NEWTAG=${OLDTAG//-/.} - echo -e "$REV $NEWTAG\n$REV $OLDTAG\n0000000000000000000000000000000000000000 $OLDTAG" >> .hgtags + echo "$REV $NEWTAG" >> .hgtags done hg commit -m"Rename tags to match the normal version notation" -- Olaf Dabrunz (oda <at> fctrace.org) -- -- 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.
