On Thu, Jan 7, 2010 at 11:28 AM, Bram Moolenaar <[email protected]> wrote: > > I have setup a Mercurial repository. It contains the same files that > are in CVS, plus the updated runtime files. > > You can checkout the files with this command: > > hg clone https://vim.googlecode.com/hg/ vim > > For most machines you can install a Mercurial package that has the "hg" > command. More info here: http://mercurial.selenic.com/ > > The initial checkout takes a few minutes. After that updates should be > fast with: > > hg pull > hg update > > Let me know if something looks wrong. Once this is "approved" by > vim-dev I'll publish it to a larger audience.
I have never used Mercurial before. Following the instructions above on a Windows machine worked: requesting all changes adding changesets adding manifests adding file changes added 2036 changesets with 16823 changes to 2419 files (+1 heads) updating to branch default 2256 files updated, 0 files merged, 0 files removed, 0 files unresolved Only thing I might suggest for other newbies like myself, is to show to create the vim directory before running the clone command. This also demonstrates what directory level you should be at when you run the command. > You can checkout the files with this command: > mkdir vim > hg clone https://vim.googlecode.com/hg/ vim That will make it clear that you should be one directory up when you perform the checkout. After the checkout, my usual build procedure also worked using VS 2008. Dave
-- You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php
