From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Using versions instead of XEmacs codenames in User-Agent (was: [PATCH] SXEmacs User-Agent string)
Date: Thu, 06 Jan 2005 14:41:52 +0100 [thread overview]
Message-ID: <v9pt0iptcv.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <microsoft-free.871xczwcmk.fsf@youngs.au.com> (Steve Youngs's message of "Thu, 06 Jan 2005 11:49:07 +1000")
On Thu, Jan 06 2005, Steve Youngs wrote:
[ SXEmacs User-Agent string ]
> Does anybody have any objections to me committing this? I'll wait a
> couple of days before committing, just in case.
[ No objection from my side, just a closely related suggestion. ]
The XEmacs codenames (Rational FORTRAN, Corporate Culture, Security
Through Obscurity, ...) lead to very long User-Agent headers, that
even are folded by Gnus:
User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Security Through
Obscurity, berkeley-unix)
User-Agent: Gnus/5.110003 (No Gnus v0.3) XEmacs/21.4 (Corporate Culture,
berkeley-unix)
User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Rational FORTRAN,
windows-nt)
I would propose to get rid of the codenames and use the full version,
say 21.4.15 or 21.4.16 instead. Beside better readability, the full
version is better for people who are not familiar with the codenames.
I have a patch around for this around (but not here, being offline).
The result would look like this:
User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4.aa (berkeley-unix)
User-Agent: Gnus/5.110003 (No Gnus v0.3) XEmacs/21.4.bb (berkeley-unix)
User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4.cc (windows-nt)
(I use the placeholders "aa", "bb", "cc" because I can't recall to
which XEmacs versions the codenames correspond.)
Unless there are objections against my suggestion, I'll install it in
the stable branch and in the trunk. Steve, I'd like to ask you to
wait for my patch and then also use full version numbers instead of
codenames for SXEmacs.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2005-01-06 13:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 1:49 [PATCH] SXEmacs User-Agent string Steve Youngs
2005-01-06 13:41 ` Reiner Steib [this message]
2005-01-06 23:00 ` Using versions instead of XEmacs codenames in User-Agent Katsumi Yamaoka
2005-01-06 23:29 ` Steve Youngs
2005-01-08 18:09 ` Reiner Steib
2005-01-09 1:28 ` Steve Youngs
2005-01-09 20:55 ` Reiner Steib
2005-01-09 23:09 ` Steve Youngs
2005-01-10 8:42 ` Bjørn Mork
2005-01-10 9:20 ` Steve Youngs
2005-01-10 10:39 ` Bjørn Mork
2005-01-10 15:07 ` Reiner Steib
2005-01-10 23:29 ` Steve Youngs
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=v9pt0iptcv.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
/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).