From: Kees de Bruin <kees_de_bruin@tasking.nl>
Subject: Re: Quassia Gnus v0.15 is released
Date: Tue, 25 Nov 1997 07:58:55 MET [thread overview]
Message-ID: <199711250658.HAA14212@kouvola.tasking.nl> (raw)
In-Reply-To: <m3iutinpyt.fsf@sparky.gnus.org>
I had problems applying the patches to a clean 0.14 tree. There is still a
ChangeLog entry in the lisp/ChangeLog file for the 0.1 release at the start
of the file. Also the lisp/gnus-sum.el file couldn't be patched correctly
as it didn't contain the typo (double dot at the end of the line) in the
docstring of the function `gnus-summary-next-unread-same-subject'.
--
Kees de Bruin Software Engineer
---------------------------------------------------------------------------
E-mail: kees_de_bruin@tasking.com Tasking Software BV
Voice: +31-33-455 85 84 Plotterweg 31
Fax: +31-33-455 00 03 3821 BB Amersfoort
WWW: http://www.tasking.com The Netherlands
---------------[ Someday you'll look back on this and laugh ]--------------
next parent reply other threads:[~1997-11-25 6:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3iutinpyt.fsf@sparky.gnus.org>
1997-11-25 6:58 ` Kees de Bruin [this message]
1997-11-25 19:05 ` Lars Magne Ingebrigtsen
1997-11-24 17:47 Lars Magne Ingebrigtsen
1997-11-25 2:47 ` SL Baur
1997-11-25 19:04 ` 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=199711250658.HAA14212@kouvola.tasking.nl \
--to=kees_de_bruin@tasking.nl \
/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).