Gnus development mailing list
 help / color / mirror / Atom feed
From: Paul Graham <pjg@acsu.buffalo.edu>
Cc: "\(ding\) Gnus Mailing List" <ding@gnus.org>,
	XEmacs Beta Discussion List <xemacs-beta-discuss@xemacs.org>
Subject: Re: gnus date suggestion
Date: 02 May 1997 00:53:47 -0400	[thread overview]
Message-ID: <rig1w6cw4k.fsf@urth.acsu.buffalo.edu> (raw)
In-Reply-To: jason@mastaler.com's message of 01 May 1997 10:21:27 -0400


since both of the are legal (by my reading of rfcs 822 and 1123) i don't
understand the objection to the gnus format.

    jason> I still think the Gnus "Date:" header format is non-standard.  I
    jason> also noticed VM 6.29 under 19.15 XEmacs Lucid doesn't have this
    jason> limitation.

    jason> Gnus = Date: 01 May 1997 09:40:20 -0400
    jason> VM = Date: Thu, 1 May 1997 09:53:01 -0400 (EDT)


-- 
 paul
    pjg@acsu.Buffalo.EDU    |public keys at:
                            |     http://urth.acsu.Buffalo.EDU/~pjg/key.html
    if the above contains opinions they are mine unless marked otherwise.


  parent reply	other threads:[~1997-05-02  4:53 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-01-12 19:12 Jason R. Mastaler
1997-01-12 22:07 ` David Moore
1997-01-15  1:09   ` Lars Magne Ingebrigtsen
1997-05-01 14:21   ` Jason R. Mastaler
1997-05-01 21:30     ` François Pinard
1997-05-03  4:17       ` Jason R. Mastaler
1997-05-03 14:53         ` François Pinard
1997-05-03 15:13           ` Hrvoje Niksic
1997-05-03 16:41             ` Lars Magne Ingebrigtsen
1997-05-05  6:45               ` Steinar Bang
1997-05-08 12:39                 ` Lars Magne Ingebrigtsen
1997-05-03 17:31             ` Jason R. Mastaler
1997-08-05 23:07             ` François Pinard
     [not found]               ` <x73eooi146.fsf@peorth.gweep.net>
1997-08-08  5:43                 ` Greg Stark
1997-05-03 15:35           ` Johan Danielsson
1997-08-05 22:59             ` François Pinard
1997-08-06 23:11               ` Kyle Jones
1997-08-07 16:32                 ` Johan Danielsson
1997-10-21 14:04                 ` François Pinard
1997-10-21 19:03                   ` Jason R Mastaler
1997-10-21 19:59                     ` Valdis.Kletnieks
1998-02-08 19:06                     ` François Pinard
1998-02-08 19:55                       ` Lars Magne Ingebrigtsen
1998-02-08 20:09                       ` Kyle Jones
1998-02-09  1:13                         ` François Pinard
1998-02-09 10:06                           ` Per Abrahamsen
1998-02-09 15:31                           ` Lars Magne Ingebrigtsen
1998-02-08 22:53                       ` Jason R Mastaler
1998-02-09  3:49                       ` Stephen J. Turnbull
1998-02-09 15:49                         ` Lars Magne Ingebrigtsen
1997-05-03  8:14       ` David Moore
1997-05-04  0:00       ` Ken Raeburn
1997-05-02  4:53     ` Paul Graham [this message]
1997-05-02  5:17       ` Jason R. Mastaler
1997-05-03  8:19     ` David Moore
1997-05-03  8:40       ` Steven L Baur
1997-05-03  9:15         ` Hrvoje Niksic
1997-05-03  8:58       ` Per Abrahamsen

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=rig1w6cw4k.fsf@urth.acsu.buffalo.edu \
    --to=pjg@acsu.buffalo.edu \
    --cc=ding@gnus.org \
    --cc=xemacs-beta-discuss@xemacs.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.
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 NNTP newsgroup(s).