unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: JD Smith <jdsmith@as.arizona.edu>
Cc: emacs-devel@gnu.org
Subject: Re: CVS issues
Date: Sat, 29 Apr 2006 00:13:51 -0700	[thread overview]
Message-ID: <3AFC4C11-1DD7-419C-9E02-859C1D1F3F6F@as.arizona.edu> (raw)
In-Reply-To: <E1FZgTH-0006Qx-0j@fencepost.gnu.org>


On Apr 28, 2006, at 8:50 PM, Richard Stallman wrote:

> How often does this problem occur?
> Is it days apart?  Weeks?  Months?
>
> Since the bug is not reproducible, I think the only way to fix it
> is to add more instrumentation code.

To be honest, I'm not sure.  I've had it happen at least three  
separate times, and typically it persists for a day or more,  
sporadically occurring, approximately half the time.  But it hasn't  
happened in several weeks (though my CVS usage varies considerably).   
My strong suspicion is that this relates to a persistent behavior of  
the CVS host, timing out or otherwise generating some situation which  
CVS Emacs cannot cope with well, but it hasn't repeated enough to  
allow honing in on the problem.  I've tried disconnecting the network  
to set cvs up to fail, but now all I get is the correct standard  
error message.  Since people reading this list no doubt exercise cvs  
via Emacs far more than I do, the fact that many others haven't  
echoed the problem makes me think it might be incredibly rare, or  
pertain to my specific setup in some unknown way.  I'll stay on the  
lookout for it.

      reply	other threads:[~2006-04-29  7:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-17 19:34 CVS issues JD Smith
2006-04-17 19:36 ` JD Smith
2006-04-17 20:58   ` Stefan Monnier
2006-04-17 21:13     ` JD Smith
2006-04-25 16:48 ` Richard Stallman
2006-04-25 17:42   ` JD Smith
2006-04-29  3:50     ` Richard Stallman
2006-04-29  7:13       ` JD Smith [this message]

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=3AFC4C11-1DD7-419C-9E02-859C1D1F3F6F@as.arizona.edu \
    --to=jdsmith@as.arizona.edu \
    --cc=emacs-devel@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).