unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <turnbull@sk.tsukuba.ac.jp>
To: rms@gnu.org
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] /srv/bzr/emacs/trunk r104691: Don't reuse previous Message-id when resending.
Date: Tue, 28 Jun 2011 10:31:32 +0900	[thread overview]
Message-ID: <87oc1i213f.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <E1QbKq5-0001To-NO@fencepost.gnu.org>

Richard Stallman writes:

 > You are wasting your time trying to argue from authority.

Please, stop using offensive language.  It clouds your mind. ;-)
"Authority" has no connection to this issue.

*None* of my arguments depend on "authority".  *You explicitly agreed
with the principal statement of the RFC* ("the sender's intention
rules").  How can there be any issue of "authority" when in fact we
agree on the right thing at that level?  The RFC does not go beyond
that (except to explicitly disclaim that analysis of content can be
sufficient to determine sender's intent).

The point is that, contrary to your claim, the behavior you installed
is *not* harmless, it does occasional, but specific, predictable, and
widespread, harm to the users of threading MUAs.  Stefan referred to
it, I've described it, Uday has described it.  It's real.  It is not
"dealt with reasonably" by existing MUAs, and cannot be.

OTOH, you have cited a past inconvenience involving only you and a
certain program, whose details you don't even remember.  I'm sure it
was a real issue, but hardly a justification for changing this default
IMO.

I think there is good reason here for you to reconsider.



  reply	other threads:[~2011-06-28  1:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1QZnWt-0001JW-56@colonialone.fsf.org>
2011-06-25 13:32 ` [Emacs-diffs] /srv/bzr/emacs/trunk r104691: Don't reuse previous Message-id when resending Stefan Monnier
2011-06-25 20:14   ` Glenn Morris
2011-06-26 16:17   ` Richard Stallman
2011-06-27  7:17     ` Stephen J. Turnbull
2011-06-27 16:28       ` Richard Stallman
2011-06-27 17:47         ` Uday S Reddy
2011-06-28 16:14           ` Richard Stallman
2011-06-27 20:28         ` Stephen J. Turnbull
2011-06-27 23:03           ` Richard Stallman
2011-06-28  1:31             ` Stephen J. Turnbull [this message]
2011-06-28  1:45             ` Daniel Colascione
2011-06-28  2:56               ` Eli Zaretskii
2011-06-28 13:28                 ` Uday S Reddy
2011-06-28 17:17                   ` Eli Zaretskii
2011-06-29 21:40                     ` David Kastrup
2011-06-28 16:13               ` Richard Stallman
2011-06-28 17:51                 ` Richard Riley
2011-06-29 10:57                   ` Richard Stallman
2011-06-30 16:46     ` Stefan Monnier

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=87oc1i213f.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=turnbull@sk.tsukuba.ac.jp \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --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).