From: Patrick Drechsler <patrick.drechsler@gmx.net>
Subject: Re: Now that No Gnus is imminent ...
Date: Sat, 03 Jan 2004 03:27:59 +0100 [thread overview]
Message-ID: <m3hdzdhikw.fsf@pdrechsler.fqdn.th-h.de> (raw)
In-Reply-To: <plop87ad55sst5.fsf@gnu-rox.org>
Xavier Maillard wrote on 03 Jan 2004 02:51:34 MET:
> On 3 Jan 2004, Wes Hardaker<wes@hardakers.net> said:
>>>>>>> On Fri, 02 Jan 2004 22:46:02 +0100, Lars Magne Ingebrigtsen
>>>>>>> <larsi@gnus.org> said:
>>
>>>> ... do you folks think that the "No gnus is bad news" message in
>>>> `gnus-group.el' and `gnus-sum.el' should be changed to something
>>>> more appropriate? ... such as "No Gnus is good news", perhaps?
>>
>> Lars> Or "No Gnus is Good Gnus".
>>
>> "No Gnus is Good Gnus; No news is bad news"
>
> I love this one and will use it as a signature attachment :)
>
>> "I now know my new news through no gnus news"?
>
> Hmmm weird ;)
>
>> I'm partial to the last, though its quite different than the previous
>> phrase unlike the first.
>
> I vote for your first proposition :)
Consumer Voice: I second that.
I'm having enough "trouble" reading the Manual. It's nice to read
though... But it takes forever.
BTW: My attempts to cvs update have not resulted in Gnus
5.10.x4. Is there a something I'm missing? Or is this something
that only developers should be using? Apart from what is going
to happen on Sunday...
Patrick
--
There are two major products that come out of Berkeley: LSD and UNIX.
We don't believe this to be a coincidence.
Jeremy S. Anderson
next prev parent reply other threads:[~2004-01-03 2:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-02 21:34 Lloyd Zusman
2004-01-02 21:46 ` Lars Magne Ingebrigtsen
2004-01-02 23:43 ` Wes Hardaker
2004-01-03 1:51 ` Xavier Maillard
2004-01-03 2:27 ` Patrick Drechsler [this message]
2004-01-03 19:41 ` Lars Magne Ingebrigtsen
2004-01-03 19:46 ` Lars Magne Ingebrigtsen
2004-01-04 11:06 ` Patrick Drechsler
2004-01-03 20:48 ` Steve Youngs
2004-01-03 15:03 ` Andrew Korty
2004-01-03 15:34 ` Ralf Angeli
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=m3hdzdhikw.fsf@pdrechsler.fqdn.th-h.de \
--to=patrick.drechsler@gmx.net \
/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).