From: Miles Bader <miles@lsi.nec.co.jp>
Cc: emacs-devel@gnu.org
Subject: Re: [spiegel@gnu.org: Re: [Fwd: vc-annotate causes Emacs to die]]
Date: 29 Aug 2002 16:36:39 +0900 [thread overview]
Message-ID: <buou1lektfc.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <20020829082543.D6FB.LEKTU@terra.es>
Juanma Barranquero <lektu@terra.es> writes:
> Last time it happened, there was some talk about installing a cron job
> that could delete such locks after a while. Why has not been done? Lack
> of time, or a technical problem of some sort with the proposed fix?
Usually it seems to come down to:
* The people who have access to the machine either don't care or
don't have time
* The people who care and have time don't have access to the machine
* By the time the latter group can get access, they've either run out
of time, or stopped caring
and of course
* Talk is cheap
-Miles
--
`Life is a boundless sea of bitterness'
next prev parent reply other threads:[~2002-08-29 7:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-26 0:36 [spiegel@gnu.org: Re: [Fwd: vc-annotate causes Emacs to die]] Richard Stallman
2002-08-26 13:33 ` Gerd Moellmann
2002-08-26 18:26 ` vc-annotate causes Emacs to die Andre Spiegel
2002-08-26 18:35 ` [spiegel@gnu.org: Re: [Fwd: vc-annotate causes Emacs to die]] Alan Shutko
2002-08-26 20:25 ` Gerd Moellmann
2002-08-26 22:02 ` Gerd Moellmann
2002-08-27 1:59 ` Miles Bader
2002-08-27 10:31 ` Gerd Moellmann
2002-08-28 1:15 ` Miles Bader
2002-08-28 10:07 ` Gerd Moellmann
2002-08-27 15:56 ` Kim F. Storm
2002-08-27 15:50 ` Gerd Moellmann
2002-08-27 19:05 ` Richard Stallman
2002-08-27 23:35 ` Alan Shutko
2002-08-28 23:32 ` Richard Stallman
2002-08-29 6:27 ` Juanma Barranquero
2002-08-29 7:36 ` Miles Bader [this message]
2002-08-28 10:12 ` Gerd Moellmann
2002-08-28 23:33 ` Richard Stallman
2002-08-30 13:15 ` Kim F. Storm
2002-08-27 19:05 ` Richard Stallman
2002-08-28 10:32 ` Gerd Moellmann
2002-08-28 23:33 ` Richard Stallman
2002-08-29 9:51 ` Gerd Moellmann
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=buou1lektfc.fsf@mcspd15.ucom.lsi.nec.co.jp \
--to=miles@lsi.nec.co.jp \
--cc=emacs-devel@gnu.org \
--cc=miles@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).