Gnus development mailing list
 help / color / mirror / Atom feed
From: deskpot@myrealbox.com (Vasily Korytov)
Subject: Re: [patch] gnus-boring-article-headers: to-list and cc-list
Date: Sat, 01 Mar 2003 02:04:55 +0300	[thread overview]
Message-ID: <877kbk0zxk.fsf@unix.home> (raw)
In-Reply-To: <2n65r42kj5.fsf@zsh.cs.rochester.edu> (ShengHuo ZHU's message of "Fri, 28 Feb 2003 15:54:38 -0500")


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

>>>>> "ZSH" == ShengHuo ZHU writes:

 ZSH> The patch looks fine.  Could you please sign the copyright assignment
 ZSH> so that we can install the patch?  I'll send you the detail in another
 ZSH> email.

Sure.

 ZSH> Also could you make a patch to the texi file too?

Here it goes.


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

--- gnus.texi~	Fri Feb 28 21:36:09 2003
+++ gnus.texi	Sat Mar  1 01:59:45 2003
@@ -10538,6 +10538,12 @@
 @item to-address
 Remove the @code{To} header if it only contains the address identical to
 the current groups's @code{to-address} parameter.
+@item to-list
+Remove the @code{To} header if it only contains the address identical to
+the current groups's @code{to-list} parameter.
+@item cc-list
+Remove the @code{CC} header if it only contains the address identical to
+the current groups's @code{to-list} parameter.
 @item date
 Remove the @code{Date} header if the article is less than three days
 old.

[-- 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-28 23:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-28 18:51 Vasily Korytov
2003-02-28 20:54 ` ShengHuo ZHU
2003-02-28 23:04   ` Vasily Korytov [this message]

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=877kbk0zxk.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).