From: Lee Cantey <lcantey@borland.com>
Subject: Re: mail attachments not attached - gnus-5.8.6
Date: 25 May 2000 10:35:06 -0700 [thread overview]
Message-ID: <m31z2q354l.fsf@neo.inprise.com> (raw)
In-Reply-To: <vaf7lckb2n7.fsf@lucy.cs.uni-dortmund.de>
>>>>> On Wed May 24, Kai writes:
> Miroslav Zubcic <miroslav.zubcic@zesoi.fer.hr> writes:
>> Sorry, but I realy don't know how to use CVS. Or 5.8.7 is out
>> already?
I too ran into this problem (painfully). It doesn't appear that 5.8.7
is out yet.
> You don't need to use CVS if you don't want to. ftp.gnus.org
> contains a snapshots directory which contains normal tarballs,
> except that these are automatically created every night, without any
> testing at all.
That's a good workaround (I just pulled CVS and kept on going). But I
feel that this bug alone is enough of a problem to warrant a new 5.8.7
release. Lars, are you there?
Lee.
next prev parent reply other threads:[~2000-05-25 17:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-23 21:17 Miroslav Zubcic
2000-05-24 6:25 ` Peter Weiss - Sun Germany ENS Engineer Mission Critical - Munich
2000-05-24 11:26 ` Miroslav Zubcic
2000-05-24 11:37 ` Kai Großjohann
2000-05-25 17:35 ` Lee Cantey [this message]
2000-05-25 18:54 ` Miroslav Zubcic
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=m31z2q354l.fsf@neo.inprise.com \
--to=lcantey@borland.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).