From: Eli Zaretskii <eliz@gnu.org>
To: Dave Abrahams <dave@boostpro.com>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Proposed patch: allow user to disable lockfile creation
Date: Sat, 30 Jul 2011 10:21:23 +0300 [thread overview]
Message-ID: <83y5zgcjyk.fsf@gnu.org> (raw)
In-Reply-To: <m2ipqksaxp.fsf@pluto.luannocracy.com>
> From: Dave Abrahams <dave@boostpro.com>
> Date: Fri, 29 Jul 2011 23:29:38 -0400
> Cc: johnw@newartisans.com, theophilusx@gmail.com, lennart.borgman@gmail.com,
> emacs-devel@gnu.org, schwab@linux-m68k.org, stephen@xemacs.org
>
> I'm sure that depends on your perspective about what's convenient. The
> advance warning feature may be convenient for you, but for me (and
> apparently I'm not alone) it's a nuisance. My patch simply allows
> people to turn this feature off if they have the same experience as I
> do. Is there some reason it can't be accepted?
You can always disable this feature by removing the CLASH_DETECTION
macro definition on the appropriate header file in src/s/, can't you?
next prev parent reply other threads:[~2011-07-30 7:21 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 2:42 Proposed patch: allow user to disable lockfile creation Dave Abrahams
2011-07-27 15:32 ` Andreas Schwab
2011-07-27 16:25 ` Dave Abrahams
2011-07-27 18:56 ` John Wiegley
2011-07-28 1:57 ` Stephen J. Turnbull
2011-07-28 16:46 ` Richard Stallman
2011-07-28 16:54 ` Lennart Borgman
2011-07-28 23:00 ` Richard Stallman
2011-07-29 0:12 ` Tim Cross
2011-07-29 0:51 ` Dave Abrahams
2011-07-29 23:40 ` Richard Stallman
2011-07-30 3:29 ` Dave Abrahams
2011-07-30 7:21 ` Eli Zaretskii [this message]
2011-07-30 12:32 ` Dave Abrahams
2011-07-30 18:12 ` Richard Stallman
2011-07-31 2:13 ` Tim Cross
2011-07-29 23:40 ` Richard Stallman
2011-07-30 12:46 ` Dave Abrahams
2011-07-28 18:22 ` chad
2011-07-28 23:00 ` Richard Stallman
2011-07-28 19:21 ` Paul Eggert
2011-07-29 17:31 ` Richard Stallman
2011-07-29 19:59 ` David Kastrup
2011-07-30 4:35 ` Richard Stallman
2011-07-30 7:36 ` David Kastrup
2011-07-29 3:31 ` Stephen J. Turnbull
2011-07-28 21:20 ` Evil Boris
2011-07-30 14:20 ` Daniel Colascione
2011-07-30 18:12 ` Richard Stallman
2011-07-31 2:22 ` Tim Cross
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=83y5zgcjyk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dave@boostpro.com \
--cc=emacs-devel@gnu.org \
--cc=rms@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).