From: Jason Molenda <jason-gcclist@molenda.com>
To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>, overseers@gcc.gnu.org
Subject: Re: GCC ssh/cvs account problem
Date: Tue, 18 Feb 2003 21:05:00 -0000 [thread overview]
Message-ID: <20030218130512.A94670@molenda.com> (raw)
In-Reply-To: <20030218200936.GC9191@redhat.com>; from cgf@redhat.com on Tue, Feb 18, 2003 at 03:09:36PM -0500
On Tue, Feb 18, 2003 at 03:09:36PM -0500, Christopher Faylor wrote:
> I have already forwarded your request to overseers@gcc.gnu.org. I'm
> cc'ing this message there.
>
> Nothing has changed on your account for years, so I don't know
> why you are having problems unless you changed your key or protocol.
I don't have anything to suggest, really. You can enable cvs' 'trace'
mode like
cvs -t update
where it will show all the client/server commands as they're issued.
There might be a hint in the stream somewhere. You can also have
cvs store all the stuff it sends/receives by setting the environment
variable CVS_CLIENT_LOG to a filename (/tmp/log, say). /tmp/log.in
and /tmp/log.out will be created with all the text sent over the wire
during the cvs command's execution.
Other than that, I don't have any suggestions--as far as I know,
nothing has changed on the sourceware set up in the last few weeks
and no one else is having problems like this..
J
next prev parent reply other threads:[~2003-02-18 21:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200302150454.h1F4sEj05529@caip.rutgers.edu>
[not found] ` <200302182000.h1IK0mL20688@caip.rutgers.edu>
2003-02-18 20:11 ` Christopher Faylor
2003-02-18 21:05 ` Jason Molenda [this message]
2003-02-19 0:15 ` Kaveh R. Ghazi
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=20030218130512.A94670@molenda.com \
--to=jason-gcclist@molenda.com \
--cc=ghazi@caip.rutgers.edu \
--cc=overseers@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).