all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Cc: emacs-devel@gnu.org
Subject: Re: MAIL_USE_FLOCK and Debian.
Date: Tue, 18 Feb 2003 09:58:05 -0600	[thread overview]
Message-ID: <87el657f8y.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <E18l8Hg-0001uV-00@fencepost.gnu.org> (Richard Stallman's message of "Tue, 18 Feb 2003 08:59:44 -0500")

Richard Stallman <rms@gnu.org> writes:

> I thought we had just three alternatives to consider: liblockfile,
> and the two alternatives now implemented in movemail.  Now you seem
> to be proposing additional alternatives.  I am not sure exactly what
> they are; it sounds like you propose that movemail do more than one
> of those three.  Why do you propose that?

If there are only three relevant strategies, then my comments are
irrelevant.  I just wasn't sure.  I wasn't sure that movemail offered
only 2 choices since I hadn't yet looked carefully enough to be
certain that there weren't some combinations #ifdefs that would allow
hybrid strategies like "flock then dotlock" or the reverse, on some
platforms, and I also didn't know if local admins might need (or if we
cared to try to support) custom policies.  If we were using elisp,
then we wouldn't have to decide, since customization would be easy,
but since we're probably not, we'll need to make sure we provide a
complete set of strategies.

However, if movemail only needs (and allows) two strategies normally,
and if adding support for liblockfile to that set then covers all the
relevant cases, then we should be OK.

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592  F9A0 25C8 D377 8C7E 73A4

  reply	other threads:[~2003-02-18 15:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-15  7:02 MAIL_USE_FLOCK and Debian Rob Browning
2003-02-15 19:11 ` Richard Stallman
2003-02-15 20:26   ` Rob Browning
2003-02-17  7:20     ` Richard Stallman
2003-02-17 15:31       ` Rob Browning
2003-02-17 21:20         ` Florian Weimer
2003-02-17 21:32           ` Rob Browning
2003-02-17 21:41             ` Florian Weimer
2003-02-17 21:56           ` Alan Shutko
2003-02-17 22:20             ` Rob Browning
2003-02-18 16:03           ` Rob Browning
2003-02-18 13:59         ` Richard Stallman
2003-02-18 15:58           ` Rob Browning [this message]
2003-02-19  7:16             ` Richard Stallman
2003-02-19 17:11               ` Rob Browning
2003-02-19 18:03                 ` David Masterson
2003-02-20 18:21                 ` Richard Stallman
2003-02-20 19:22                   ` Rob Browning
2003-02-21 21:44                     ` Richard Stallman
2003-02-24  2:58                       ` Rob Browning
2003-02-28  8:14                       ` Michael Sperber [Mr. Preprocessor]
2003-03-01 21:44                         ` Richard Stallman
2003-03-02 10:06                           ` Michael Sperber [Mr. Preprocessor]
2003-03-03 18:58                             ` Richard Stallman
2003-03-04  8:30                               ` Michael Sperber [Mr. Preprocessor]
2003-03-05 20:46                                 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87el657f8y.fsf@raven.i.defaultvalue.org \
    --to=rlb@defaultvalue.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.