From: Mike Shaver <shaver@netscape.com>
To: Alex deVries <adevries@engsoc.carleton.ca>,
Ulf Carlsson <grimsy@zigzegv.ml.org>,
linux@cthulhu.engr.sgi.com
Subject: Re: cvs
Date: Wed, 10 Jun 1998 16:04:17 -0400 [thread overview]
Message-ID: <357EE6C1.A424FC67@netscape.com> (raw)
In-Reply-To: 357DA057.AB9EF73B@netscape.com
Mike Shaver wrote:
> I'll do that right now...
And I did (almost right away, even!).
cvs -d :pserver:cvs@linus.linux.sgi.com:/cvs login
(password is "cvs")
cvs -d :pserver:cvs@linus.linux.sgi.com:/cvs co linux
Although CVS doesn't appear to be honouring the CVSROOT/readers file,
:pserver: checkins don't succeed because there's no /var/tmp in the
chroot'd area. Not optimal, but it keeps things safe for now.
Mike
--
190678.54 157843.71
next prev parent reply other threads:[~1998-06-10 20:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-06-09 0:05 Swamped ralf
1998-06-09 19:19 ` cvs Ulf Carlsson
1998-06-09 19:34 ` cvs Alex deVries
1998-06-09 19:45 ` cvs Alex deVries
1998-06-09 20:51 ` cvs Mike Shaver
1998-06-10 20:04 ` Mike Shaver [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-09-07 18:57 cvs Ulf Carlsson
1999-06-13 16:55 CVS Ralf Baechle
1999-06-13 18:31 ` CVS Ulf Carlsson
1999-06-13 21:10 ` CVS Ralf Baechle
1999-09-30 21:15 CVS Ralf Baechle
2000-05-15 10:08 CVS Ruedi.Hofer
2000-05-15 22:49 ` CVS Pavel Roskin
2002-06-20 14:04 CVS Eduardo Frias
2002-06-20 15:09 ` CVS Tim Walberg
2002-10-21 15:02 cvs Hill, John
2003-01-17 12:16 CVS Pieter Palmers
2003-01-17 18:02 ` CVS Roger Williams
2003-01-17 18:25 ` CVS Roger Williams
2003-01-19 17:47 ` CVS iriXx
2003-01-19 18:33 ` CVS Roger Williams
2003-01-21 8:45 cvs bulent acikgoz
2005-05-19 6:24 CVS Philip Edelbrock
2005-05-19 6:24 ` CVS Philip Edelbrock
2005-05-19 6:24 ` CVS Jean Delvare
2005-05-19 6:24 ` CVS Jean Delvare
2006-05-02 2:03 CVS Tom McCabe
2006-05-02 2:12 ` CVS Jody
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=357EE6C1.A424FC67@netscape.com \
--to=shaver@netscape.com \
--cc=adevries@engsoc.carleton.ca \
--cc=grimsy@zigzegv.ml.org \
--cc=linux@cthulhu.engr.sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.