From: Kai Grossjohann <kai@emptydomain.de>
Subject: Re: how to debug an emacs hang?
Date: Sat, 22 May 2004 21:09:43 +0200 [thread overview]
Message-ID: <86ekpce0so.fsf@rumba.de.uu.net> (raw)
In-Reply-To: uekpebt76.fsf@ece.ucdavis.edu
John Owens <john_owens@yahoo.com> writes:
> One difficulty with that approach is that if I'm getting source from
> CVS it's always a little dicey to make sure I have a stable version,
> since I might have got new files in the middle of a checkin.
I'm surprised, I can't remember that this ever happened to me. Did
it happen to you?
You could run "cvs update" again after a few seconds, and if nothing
changes then you guess that you're not in the middle of a checkin.
Kai
prev parent reply other threads:[~2004-05-22 19:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 23:38 how to debug an emacs hang? John Owens
2004-05-19 0:03 ` Miles Bader
2004-05-19 7:08 ` Eli Zaretskii
2004-05-19 7:48 ` Jason Rumney
2004-05-20 22:59 ` John Owens
2004-05-22 19:09 ` Kai Grossjohann [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=86ekpce0so.fsf@rumba.de.uu.net \
--to=kai@emptydomain.de \
/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).