From: Benjamin Rutt <rutt+news@cis.ohio-state.edu>
Subject: Re: "subscribed" has overloaded meaning in gnus?
Date: Fri, 11 Jan 2002 21:14:13 -0500 [thread overview]
Message-ID: <wc3bsg0z56y.fsf@eta.cis.ohio-state.edu> (raw)
In-Reply-To: <87ita9kqg9.fsf@cs.utah.edu>
Sriram Karra <karra@cs.utah.edu> writes:
> [ I had sent that MFT doc... ]
>
> This is what I will do: I will document the "subscribed" parameter in
> the Group Parameters node and include a cross reference or something
> in the MFT docs node.
Sounds like an excellent idea. Hopefully that will make it clearer to
everyone what the double-meaning of subscribed is.
> Also, it will take a while before the changes will appear in CVS...
I'm guessing you're talking about signing papers. I am eagerly
awaiting snail mail papers to arrive in my mailbox from GNU for a gnus
contribution (gnus-dired.el) of my own. Hopefully we won't have to
wait too much longer, but it's been almost a month for me already.
--
Benjamin
prev parent reply other threads:[~2002-01-12 2:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 15:49 Benjamin Rutt
2002-01-04 17:02 ` Matt Armstrong
2002-01-04 18:41 ` Benjamin Rutt
2002-01-11 12:44 ` Sriram Karra
2002-01-12 2:14 ` Benjamin Rutt [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=wc3bsg0z56y.fsf@eta.cis.ohio-state.edu \
--to=rutt+news@cis.ohio-state.edu \
/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).