From: Lars Ingebrigtsen <larsi@gnus.org>
To: Colin Baxter <m43cap@yandex.com>
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>, Bastien <bzg@gnu.org>,
34983@debbugs.gnu.org, Deus Max <deusmax@gmx.com>
Subject: bug#34983: 27.0.50; Gnus cannot start
Date: Sat, 22 Jun 2019 14:48:15 +0200 [thread overview]
Message-ID: <m336k1eqgg.fsf@gnus.org> (raw)
In-Reply-To: <87woknrn9k.fsf@yandex.com> (Colin Baxter's message of "Mon, 25 Mar 2019 15:23:35 +0000")
Colin Baxter <m43cap@yandex.com> writes:
> Ok, I've applied the patch to emacs-27.0.50 and gnus opens the nnrss feeds
> satisfactorily - as it does with my other newsgroups and the imap
> emails. There are no errors or warnings at all. I did `make clean' and
> deleted lisp/gnus/*.elc files before the final `make', so I may have
> gone overboard in the build.
OK, sounds like the problems reported here were fixed at the time, so
I'm closing this bug report. If that's a mistake, please reopen.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-06-22 12:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-24 22:09 bug#34983: 27.0.50; Gnus cannot start Bastien
2019-03-24 23:43 ` Eric Abrahamsen
2019-03-25 0:24 ` Deus Max
2019-03-25 0:36 ` Eric Abrahamsen
2019-03-25 5:04 ` Deus Max
2019-03-25 7:09 ` Colin Baxter
2019-03-25 10:54 ` Bastien
2019-03-25 12:24 ` Colin Baxter
2019-03-25 14:47 ` Eric Abrahamsen
2019-03-25 15:23 ` Colin Baxter
2019-03-25 17:12 ` Eric Abrahamsen
2019-06-22 12:48 ` Lars Ingebrigtsen [this message]
2019-06-22 15:54 ` Eric Abrahamsen
2019-03-25 15:01 ` Eric Abrahamsen
2019-03-25 17:45 ` Deus Max
2019-03-25 17:56 ` Deus Max
2019-03-25 6:36 ` Bastien
2019-03-25 13:07 ` Basil L. Contovounesios
2019-03-25 14:58 ` Eric Abrahamsen
2019-04-02 5:35 ` Bastien
2019-04-02 10:55 ` Basil L. Contovounesios
2019-04-03 0:26 ` Eric Abrahamsen
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=m336k1eqgg.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=34983@debbugs.gnu.org \
--cc=bzg@gnu.org \
--cc=deusmax@gmx.com \
--cc=eric@ericabrahamsen.net \
--cc=m43cap@yandex.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.