From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: User Agent string: making it more specific?
Date: 03 Jan 2000 09:22:19 +0100 [thread overview]
Message-ID: <rjd7rjef9g.fsf@zuse.dina.kvl.dk> (raw)
In-Reply-To: Stainless Steel Rat's message of "02 Jan 2000 18:46:00 -0500"
Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> * jari.aalto@poboxes.com (Jari Aalto+mail.emacs) on Fri, 31 Dec 1999
> | I suggest that the architecture info is added to next Gnus release
>
> Of what utility is having the system architecture included with every
> message?
I'd often use that information when making technical comments to posts
from Mozilla users, and have wished for similar information from posts
and mail from Gnus users.
next prev parent reply other threads:[~2000-01-03 8:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <wk4scz7bca.fsf@R1.JONADAB.NET>
[not found] ` <vxkg0wjjrib.fsf@beaver.jprc.com>
1999-12-31 15:45 ` Jari Aalto+mail.emacs
2000-01-02 23:46 ` Stainless Steel Rat
2000-01-03 8:22 ` Per Abrahamsen [this message]
2000-01-03 9:02 ` Eric Marsden
2000-01-03 9:12 ` Arcady Genkin
2000-01-03 9:39 ` Florian Weimer
2000-01-03 11:58 ` William M. Perry
2000-01-03 15:40 ` Stainless Steel Rat
2000-01-03 19:10 ` Kai Großjohann
2000-01-04 16:52 ` Steinar Bang
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=rjd7rjef9g.fsf@zuse.dina.kvl.dk \
--to=abraham@dina.kvl.dk \
/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).