From: thunder7@xs4all.nl
To: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] cvs update gives 'move away ....' on every file
Date: Wed, 5 Sep 2001 15:29:44 +0200 [thread overview]
Message-ID: <20010905152944.A23742@middle.of.nowhere> (raw)
- downloaded the linux-latest.tar.gz archive
- created /home/cvs/parisc and made sure I had enough permissions
- untarred the linux-latest.tar.gz archive there, creating
/home/cvs/parisc/linux
- installed cvs
- made sure there's a variable CVSROOT in my environment, value:
":pserver:anonymous@puffin.external.hp.com:/home/cvs/parisc" (without
the " of course)
- created ~/.cvsrc, containing:
cvs -z3 -q
diff -uNp
update -Pd
rm -f
- typed 'cd /home/cvs/parisc; cvs update'
result:
jurriaan@pa8200:/home/cvs/parisc$ cvs update -A
cvs update: move away linux/.cvsignore; it is in the way
C linux/.cvsignore
cvs update: move away linux/COPYING; it is in the way
C linux/COPYING
cvs update: move away linux/CREDITS; it is in the way
C linux/CREDITS
cvs [update aborted]: received interrupt signal
and so on. Comments on www.google.com and various mailin-lists seem to
indicate this is often a server-error. I can't really believe that,
since it seems to work for everyone else.
I retried it with linux-20010830.tar.gz, and the same messages were
printed.
What am I doing wrong?
Thanks,
Jurriaan
--
Cool is one thing, but you're frozen solid.
Startrek DS9: Vic Fontaine to Odo.
GNU/Linux 2.4.9-ac7 SMP/ReiserFS 2x1402 bogomips load av: 0.03 0.03 0.02
next reply other threads:[~2001-09-05 13:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-05 13:29 thunder7 [this message]
2001-09-06 5:04 ` [parisc-linux] cvs update gives 'move away ....' on every file Grant Grundler
2001-09-06 5:18 ` Andrew Shugg
2001-09-06 5:35 ` thunder7
2001-09-06 6:08 ` Grant Grundler
2001-09-06 12:53 ` Matthew Wilcox
2001-09-06 19:14 ` thunder7
2001-09-07 7:07 ` Andrew Shugg
2001-09-09 12:26 ` [parisc-linux] 'Getting a parisc-linux cvs kernel without stress' thunder7
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010905152944.A23742@middle.of.nowhere \
--to=thunder7@xs4all.nl \
--cc=parisc-linux@lists.parisc-linux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox