unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: JD Smith <jdsmith@as.arizona.edu>
Cc: rms-response-1w@gnu.org, emacs-devel@gnu.org
Subject: Re: Unreliability in CVS access
Date: Sun, 25 Jun 2006 12:36:37 -0700	[thread overview]
Message-ID: <E4F5D0AB-6A3B-4C99-B29D-F5623981E351@as.arizona.edu> (raw)
In-Reply-To: <E1FuHSp-0003Ji-Ol@fencepost.gnu.org>


On Jun 24, 2006, at 4:22 PM, Richard Stallman wrote:

> Has anyone investigated this problem?  It is a serious problem,
> which is why I put it in FOR-RELEASE.
>
> There used to be a bad interaction between CVS and SSH.
> A year ago I convinced the CVS developers to make a change
> designed to solve the problem.  Is this that same problem?
> I am not sure, but the fact that the problem never happens
> with Emacs 21 suggests the bug is in Emacs.
>
> JD Smith, are you using CVS thru SSH?
> Does the problem go away with the latest CVS?
> Does the latest CVS contain a fix for the problem
> as they discussed it a year ago?

Though I have not exercised CVS through SSH much recently, I have not  
had the problem recur (same CVS version).  My vague impression was  
that it was related to a temporary or intermittent configuration  
issue on the server (e.g. savannah) side which persisted for several  
weeks in April, but I don't have much more to go on than that.   
Stefan Monnier mentioned other reports of the same or similar  
problem, so perhaps tracking those down would yield progress.  Sorry  
I don't have more help to offer.  I will certainly keep an eye out  
for recurrence.

JD

  reply	other threads:[~2006-06-25 19:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-24 23:22 Unreliability in CVS access Richard Stallman
2006-06-25 19:36 ` JD Smith [this message]
2006-06-26 11:33   ` Richard Stallman

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E4F5D0AB-6A3B-4C99-B29D-F5623981E351@as.arizona.edu \
    --to=jdsmith@as.arizona.edu \
    --cc=emacs-devel@gnu.org \
    --cc=rms-response-1w@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).