Micah Cowan wrote:
Edward L. Fox wrote:
On 5/10/07, Gautam Iyer <[EMAIL PROTECTED]> wrote:
I got the same error. My response was
rm -rf vim7
svn co https://svn.sourceforge.net/svnroot/vim/trunk vim7
"svn switch" can only switch from a directory into another directory
inside the same repository. It doesn't allow the user to switch from
one server to another server. So you will not be able to switch from
"svn.sourceforge.net" to "vim.svn.sourceforge.net". So you can try to
switch to https://svn.sourceforge.net/svnroot/vim/branches/vim7.1
Well, except that in this case, the --relocate option would probably be
appropriate, which is used to support switches between different
repositories.
I don't know. I'm still asking Bram for the latest sources. Currently,
trunk and 7.1 branch will be the same.
My understanding of what Bram said is that trunk/ already has the latest
sources. I'm not entirely sure what was meant by "runtime" files, but I
suspect he /may/ have meant: files that are generated automatically, and
are therefore potentially inappropriate to a repository.
No, the runtime files are those which go into runtime/ not src/ and are not
compiled into the binaries but copied to $VIMRUNTIME and below. Their updates
are usually not mentioned in the official patches, but their latest versions
can be had (now) by rsync. Here's the script I use (the last line is for
"cleaning up" the log by removing temporary lines which were erased as the
download progressed):
#!/bin/bash
rsync -avzcP --delete --exclude="/dos/" ftp.nluug.nl::Vim/runtime/ ./runtime/
2>&1 | tee rsync.log
vim -es -u NONE -c '%s/^.*\r//' -cx rsync.log
Beware of "beautifying" mailers! There are three lines, starting respectively
"#!/", "rsync" and "vim".
Best regards,
Tony.
--
hundred-and-one symptoms of being an internet addict:
226. You sit down at the computer right after dinner and your spouse
says "See you in the morning."
