Gnus development mailing list
 help / color / mirror / Atom feed
From: deskpot@myrealbox.com (Vasily Korytov)
Subject: Re: Changes committed gnus/lisp (ChangeLog gnus-msg.el gnus-sum.el)
Date: Sun, 09 Feb 2003 06:20:40 +0300	[thread overview]
Message-ID: <87r8ai2l87.fsf@unix.home> (raw)
In-Reply-To: <87d6m2ywwq.fsf@unix.home> (deskpot@myrealbox.com's message of "Sun, 09 Feb 2003 06:07:17 +0300")


[-- Attachment #1.1: Type: text/plain, Size: 211 bytes --]

>>>>> "VK" == Vasily Korytov writes:

 VK> [2. text/x-patch; gnus-msg.el.patch]...

I've forgotten to mention, the above patch also fixes the forgotten
concat in my code. =)) Also here goes the doc patch:

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: gnus.texi.patch --]
[-- Type: text/x-patch, Size: 721 bytes --]

--- gnus.texi~	Sun Feb  9 05:47:41 2003
+++ gnus.texi	Sun Feb  9 06:17:13 2003
@@ -11158,10 +11158,10 @@
 @item gnus-version-expose-system
 @vindex gnus-version-expose-system
 
-Your system type (@code{system-configuration} variable, such as
-@samp{i686-pc-linux}) is exposed in the auto-generated by default
-User-Agent header. Sometimes, it may be desireable (mostly because of
-aesthetic reasons) to turn it off. In this case, set it to @code{nil}.
+Your system type (@code{system-type} variable) is exposed in the
+auto-generated by default User-Agent header. Sometimes, it may be
+desireable (mostly because of aesthetic reasons) to turn it off. In this
+case, set it to @code{nil}.
 
 @end table
 

[-- Attachment #1.3: Type: text/plain, Size: 141 bytes --]

-- 
       I accept RFC3156 and RFC1991-compatible encrypted mail.
PGP key fingerprint: 123A 7CCE 6E26 6233 0D87 E01A A0F8 3524 FCD8 1841

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2003-02-09  3:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E18h9EM-0004hv-00@quimby.gnus.org>
2003-02-07 20:05 ` Jesper Harder
2003-02-07 20:29   ` Lars Magne Ingebrigtsen
2003-02-08  3:43     ` Vasily Korytov
2003-02-08  5:13     ` Jesper Harder
2003-02-08 20:47       ` Lars Magne Ingebrigtsen
2003-02-09  3:07         ` Vasily Korytov
2003-02-09  3:20           ` Vasily Korytov [this message]
2003-02-10  8:33           ` Vasily Korytov
2003-02-10  8:41             ` Russ Allbery
2003-02-10  9:10               ` Vasily Korytov
2003-02-11  1:32           ` Lars Magne Ingebrigtsen
2003-02-11  5:10             ` Jesper Harder
2003-02-11 13:23               ` User-Agent string (was: Changes committed gnus/lisp (ChangeLog gnus-msg.el gnus-sum.el)) Reiner Steib
2003-02-12 10:19                 ` User-Agent string Vasily Korytov
2003-02-22 20:27                 ` Lars Magne Ingebrigtsen
2003-02-24 21:12                   ` Reiner Steib
2003-02-24 22:18                     ` Vasily Korytov
2003-02-27 14:50                       ` Reiner Steib
2003-02-27 19:33                         ` Vasily Korytov
2003-02-28 19:26                         ` Reiner Steib
2003-03-01 23:06                           ` Frank Haun
2003-03-03 16:18                             ` Reiner Steib
2003-02-25 10:26                     ` Kai Großjohann
2003-02-11  7:23             ` Changes committed gnus/lisp (ChangeLog gnus-msg.el gnus-sum.el) Vasily Korytov
2003-02-22 20:28               ` Lars Magne Ingebrigtsen

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=87r8ai2l87.fsf@unix.home \
    --to=deskpot@myrealbox.com \
    /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).