From: Andrea Arcangeli <andrea@suse.de>
To: CVSps@dm.cobite.com, Larry McVoy <lm@bitmover.com>,
linux-kernel@vger.kernel.org,
Andreas Gruenbacher <agruen@suse.de>
Subject: Re: kernel CVS troubles with cvsps
Date: Tue, 25 Jan 2005 18:08:35 +0100 [thread overview]
Message-ID: <20050125170835.GZ7587@dualathlon.random> (raw)
In-Reply-To: <20050125165807.GA20828@nevyn.them.org>
On Tue, Jan 25, 2005 at 11:58:07AM -0500, Daniel Jacobowitz wrote:
> FYI, I haven't tried using cvsps on the kernel CVS, but I used to use it on
> GCC - and it fell down like this on a constant basis.
Interesting, for me it always worked fine on the kernel until last
month.
> You might want to take a look at 'xcvs', by Jun Sun. It's much more
> reliable and does everything I used to use cvsps for. And generally
> faster too.
I'll check it, thanks for the info.
next prev parent reply other threads:[~2005-01-25 17:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 16:42 kernel CVS troubles with cvsps Andrea Arcangeli
2005-01-25 16:58 ` Daniel Jacobowitz
2005-01-25 17:08 ` Andrea Arcangeli [this message]
2005-01-25 17:10 ` Catalin Marinas
2005-01-25 19:09 ` Andrea Arcangeli
2005-01-27 1:14 ` Larry McVoy
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=20050125170835.GZ7587@dualathlon.random \
--to=andrea@suse.de \
--cc=CVSps@dm.cobite.com \
--cc=agruen@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox