Ben Haskell wrote: > On Fri, 4 Mar 2011, Ivan Krasilnikov wrote: > > > On Fri, Mar 4, 2011 at 22:41, meino.cramer wrote: > >> And at this point one will win 1000 points for free if knowing, how > >> to enter the version string... > >> > >> I tried > >> > >> 7.3.001 > >> r7.3.001 (like svn) > >> v7-3-001 (as used by .hg.tags) > >> > >> but without luck so far. > >> > >> What is the correct spelling here ? > > > > Type 'hg log | less' to see a list of all revisions. > > > > vim 7.3.000 is ee53a39d5896 (or 2a2ad267db08, they're the same). > > > > The hg tags stop at v7-2-235 in my version of the repo, and the last log > message for .hgtags is: > > changeset: 2029:875230a0a1bf > user: convert-repo > date: Wed Jan 06 14:58:09 2010 +0000 > summary: update tags > > That makes me think they were only carried over from SVN. Bram, when > you push new patches, are you no longer adding the tags? It would be > beneficial. Having to inspect/grep the logs is a pretty poor substitute > for being able to do: > > $ hg co v7-3-000
I haven't looked into this yet. Is there a simple way to apply a tag to a specific hg changeset version, so that you can check out that version by that tag? -- Yesterday is history. Tomorrow is a mystery. Today is a gift. That's why it is called 'present'. /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- You received this message from the "vim_use" 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
