From: "Bradley D. LaRonde" <brad@ltc.com>
To: "Pete Popov" <ppopov@pacbell.net>
Cc: <linux-mips@oss.sgi.com>
Subject: Re: cvs hang
Date: Tue, 28 Aug 2001 21:40:31 -0400 [thread overview]
Message-ID: <053801c1302b$97632a30$3501010a@ltc.com> (raw)
In-Reply-To: 3B8C3E11.8020705@pacbell.net
Not me. What CVS command line are you using?
Regards,
Brad
----- Original Message -----
From: "Pete Popov" <ppopov@pacbell.net>
To: "Pete Popov" <ppopov@mvista.com>
Cc: <linux-mips@oss.sgi.com>
Sent: Tuesday, August 28, 2001 8:57 PM
Subject: Re: cvs hang
> Pete Popov wrote:
> > Does anyone else have problems with cvs when updating from the oss tree?
> > "cvs update" always hangs in scripts/usb on my system.
>
> I take that back. It "often" hangs in scripts/usb (end of update).
>
> Pete
>
WARNING: multiple messages have this Message-ID (diff)
From: "Bradley D. LaRonde" <brad@ltc.com>
To: Pete Popov <ppopov@pacbell.net>
Cc: linux-mips@oss.sgi.com
Subject: Re: cvs hang
Date: Tue, 28 Aug 2001 21:40:31 -0400 [thread overview]
Message-ID: <053801c1302b$97632a30$3501010a@ltc.com> (raw)
Message-ID: <20010829014031.ubrAR3k1KDDRYEJyNqDhoSWSRLCuyU1p4oN_DfNVh-Q@z> (raw)
In-Reply-To: 3B8C3E11.8020705@pacbell.net
Not me. What CVS command line are you using?
Regards,
Brad
----- Original Message -----
From: "Pete Popov" <ppopov@pacbell.net>
To: "Pete Popov" <ppopov@mvista.com>
Cc: <linux-mips@oss.sgi.com>
Sent: Tuesday, August 28, 2001 8:57 PM
Subject: Re: cvs hang
> Pete Popov wrote:
> > Does anyone else have problems with cvs when updating from the oss tree?
> > "cvs update" always hangs in scripts/usb on my system.
>
> I take that back. It "often" hangs in scripts/usb (end of update).
>
> Pete
>
next prev parent reply other threads:[~2001-08-29 1:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-29 0:51 cvs hang Pete Popov
2001-08-29 0:57 ` Pete Popov
2001-08-29 1:40 ` Bradley D. LaRonde [this message]
2001-08-29 1:40 ` Bradley D. LaRonde
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='053801c1302b$97632a30$3501010a@ltc.com' \
--to=brad@ltc.com \
--cc=linux-mips@oss.sgi.com \
--cc=ppopov@pacbell.net \
/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.