From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/9734 Path: main.gmane.org!not-for-mail From: Per Abrahamsen Newsgroups: gmane.emacs.gnus.general Subject: Re: [Announce] Mine game v1.17 for Emacs Date: 31 Jan 1997 12:25:45 +0100 Organization: The Church of Emacs Sender: abraham@dina.kvl.dk Message-ID: References: , <199701310720.CAA00587@psilocin.gnu.ai.mit.edu> <199701310936.EAA01473@psilocin.gnu.ai.mit.edu> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1035149711 20198 80.91.224.250 (20 Oct 2002 21:35:11 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 21:35:11 +0000 (UTC) Cc: Richard Stallman Return-Path: Original-Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by deanna.miranova.com (8.8.5/8.8.5) with SMTP id DAA04311 for ; Fri, 31 Jan 1997 03:58:48 -0800 Original-Received: from elc1.dina.kvl.dk (elc1.dina.kvl.dk [130.225.40.228]) by ifi.uio.no with ESMTP (8.6.11/ifi2.4) id for ; Fri, 31 Jan 1997 12:27:16 +0100 Original-Received: from zuse.dina.kvl.dk (zuse.dina.kvl.dk [130.225.40.245]) by elc1.dina.kvl.dk (8.6.12/8.6.4) with ESMTP id MAA09440; Fri, 31 Jan 1997 12:17:27 +0100 Original-Received: (abraham@localhost) by zuse.dina.kvl.dk (8.6.12/8.6.4) id MAA02650; Fri, 31 Jan 1997 12:25:45 +0100 Original-To: ding@ifi.uio.no X-Face: +kRV2]2q}lixHkE{U)mY#+6]{AH=yN~S9@IFiOa@X6?GM|8MBp/ In-Reply-To: Wes Hardaker's message of 31 Jan 1997 11:23:55 +0100 Original-Lines: 10 X-Mailer: Gnus v5.4.8/Emacs 19.34 Xref: main.gmane.org gmane.emacs.gnus.general:9734 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:9734 >>>>> "RS" == Richard Stallman writes: RS> Is it desirable to make both an In-reply-to and a References RS> referring to the same message? It is very desirable to always have a proper References header, much software can do nice things with it (like threading). I doubt there is any practical use of also having an In-Reply-To header, as the software that can use it most likely also handles References.