Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: info-gnus-english@gnu.org
Subject: Re: Gnus broken in the latest Emacs build?
Date: Sat, 23 Mar 2019 20:34:01 -0700	[thread overview]
Message-ID: <87pnqhlzdi.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87h8bttcyq.fsf@pobox.com>

Bernardo <bb.mail@exemail.com.au> writes:

> Greetings,
>
> am i the only one seeing the problem with the latest Emacs build (Git commit
> dbd6490ad49b0f088d56cdd5f04178bdd62c806a) ?

No, I should have posted the notice to this group as well -- you'll need
to do a "make bootstrap" after pulling this commit, in order to flush
out stale *elc files. Either that or delete all the *elc files in
lisp/gnus, and do a regular "make".

Sorry for the inconvenience! But apparently there's no way around it...

Eric



  reply	other threads:[~2019-03-24  3:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-23 22:58 Bernardo
2019-03-24  3:34 ` Eric Abrahamsen [this message]
2019-03-25 19:51   ` Clemens Schüller
2019-03-26 13:42     ` Barry Fishman

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=87pnqhlzdi.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=info-gnus-english@gnu.org \
    /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).