From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Various simple.el patches
Date: Mon, 26 May 2003 09:48:46 -0400 [thread overview]
Message-ID: <E19KILG-0000mm-5j@fencepost.gnu.org> (raw)
In-Reply-To: <200305250500.h4P50FF13590@eel.dms.auburn.edu> (message from Luc Teirlinck on Sun, 25 May 2003 00:00:15 -0500 (CDT))
Is there some danger to inadvertently leave locks around or similar
stuff? I sometimes have heard complaints like that on emacs-devel.
I guess that must have been from doing other things. It is hard to
see that simple one-line command doing that.
If you kill the cvs job while it is doing a commit, it leaves the
directory locked. Or at least, that was true in the past.
Now I think these locks get unlocked automatically after some period
of time elapses, so the problem is not really severe any more.
next prev parent reply other threads:[~2003-05-26 13:48 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 20:31 Various simple.el patches Stefan Monnier
2003-05-14 11:44 ` Kai Großjohann
2003-05-14 12:42 ` Miles Bader
2003-05-14 13:58 ` Kai Großjohann
2003-05-14 14:48 ` Miles Bader
2003-05-14 15:54 ` Kai Großjohann
2003-05-16 3:51 ` Richard Stallman
2003-05-16 5:54 ` Kai Großjohann
2003-05-17 13:49 ` Richard Stallman
2003-05-18 15:38 ` Kai Großjohann
2003-05-19 2:11 ` Luc Teirlinck
2003-05-19 7:42 ` Kai Großjohann
2003-05-19 14:22 ` Luc Teirlinck
2003-05-21 3:12 ` Luc Teirlinck
2003-05-21 14:07 ` Luc Teirlinck
2003-05-21 18:06 ` Tak Ota
2003-05-21 18:16 ` Luc Teirlinck
2003-05-21 18:33 ` Luc Teirlinck
2003-05-21 18:44 ` Luc Teirlinck
2003-05-22 2:52 ` Luc Teirlinck
2003-05-23 3:52 ` Luc Teirlinck
2003-05-23 6:57 ` Kai Großjohann
2003-05-23 18:27 ` Luc Teirlinck
2003-05-23 19:04 ` Kai Großjohann
2003-05-23 19:45 ` Luc Teirlinck
2003-05-28 4:32 ` Luc Teirlinck
2003-05-28 18:46 ` Kai Großjohann
2003-05-28 19:47 ` Luc Teirlinck
2003-05-28 20:11 ` Kai Großjohann
2003-05-30 0:50 ` Richard Stallman
2003-05-24 10:00 ` Eli Zaretskii
2003-05-25 2:42 ` Luc Teirlinck
2003-05-25 3:33 ` Eli Zaretskii
2003-05-25 4:43 ` Luc Teirlinck
2003-05-25 5:00 ` Luc Teirlinck
2003-05-26 13:48 ` Richard Stallman [this message]
2003-05-25 17:08 ` Eli Zaretskii
2003-05-25 15:06 ` Stefan Monnier
2003-05-25 15:04 ` Stefan Monnier
2003-05-23 18:47 ` Luc Teirlinck
2003-05-23 13:51 ` Stefan Monnier
2003-05-23 17:06 ` Luc Teirlinck
2003-05-23 19:07 ` Kai Großjohann
2003-05-23 19:24 ` Kai Großjohann
2003-05-23 19:39 ` Luc Teirlinck
2003-05-24 23:20 ` Richard Stallman
2003-05-27 17:43 ` Kevin Rodgers
2003-05-28 23:58 ` Richard Stallman
2003-05-14 16:38 ` Ami Fischman
2003-05-14 17:38 ` Stefan Monnier
2003-05-16 3:51 ` Richard Stallman
2003-05-15 15:40 ` Jan Nieuwenhuizen
2003-05-15 15:45 ` Stefan Monnier
2003-05-16 15:47 ` Richard Stallman
2003-05-16 18:18 ` Stefan Monnier
2003-05-18 12:22 ` Richard Stallman
2003-05-18 15:13 ` Kai Großjohann
2003-05-19 14:53 ` 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=E19KILG-0000mm-5j@fencepost.gnu.org \
--to=rms@gnu.org \
--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).