On 07/01/2010 22:08, Bram Moolenaar wrote:
Mike Williams wrote:
On 07/01/2010 16:28, Bram Moolenaar 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 get a bunch of the following warnings from cloning to a Windows machine:
WARNING: runtime/macros/hanoi/hanoi.vim already has CRLF line endings
and does not need EOL conversion by the win32text plugin.
Before your next commit, please reconsider your encode/decode settings in
Mercurial.ini or H:\vim\vim\.hg\hgrc.
I have no special encode/decode settings (checked all the config files),
just what comes out of the box with Mercurial.
This is surprising as I have a private Unix based Mercurial repository
for 7.2 patches and don't see this problem pulling to the Windows box.
Could it be from a setting on the repository being pulled from?
I don't see this problem (on Windows 7, using Mercurial 1.4.2).
Building with MingW works.
Perhaps your Mercurial is older?
Running Hg on XP Sp2 with Mercurial Distributed SCM (version
1.4.1+20091201). It would be a pain if a month old version causes problems.
I'll investigate a bit more my end. FTR a clone to a OBSD box had no
problems. I'll see what happens when I clone from that to my Windows box.
Mike
--
Prism: Place for light rays that commit minor refractions.
--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
