unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: Michael Heerdegen <michael_heerdegen@web.de>, 36903@debbugs.gnu.org
Subject: bug#36903: 27.0.50; gnus registry vs. debbugs
Date: Fri, 04 Oct 2019 10:24:38 +0200	[thread overview]
Message-ID: <87zhig6hq1.fsf@gmx.de> (raw)
In-Reply-To: <87blux2z3x.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Thu, 03 Oct 2019 16:22:42 -0700")

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

Hi Eric,

>>> Just pushed a commit that does this. The nice thing is, the unload-hook
>>> sets gnus-registry-enabled to nil, which is a better (less
>>> implementation-specific) test for whether we can rely on the registry
>>> being present or not.
>>
>> Thanks. FTR, your patch still doesn't fix my problem as reported
>> earlier.
>
> I've just pushed a patch that ought to fix that problem.

Sorry, it still doesn't work with a fresh pulled Emacs. According to git
log, your last commit is 93dd959711222cf594051fa397d6a6e324e136fc from
Oct 1. Did you forget to push?

> Thanks,
> Eric

Best regards, Michael.





  reply	other threads:[~2019-10-04  8:24 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-03  7:11 bug#36903: 27.0.50; gnus registry vs. debbugs Michael Heerdegen
2019-08-03 15:38 ` Eric Abrahamsen
2019-08-03 23:47   ` Michael Heerdegen
2019-08-04  0:16     ` Eric Abrahamsen
2019-08-04  0:27       ` Eric Abrahamsen
2019-08-04  0:44         ` Noam Postavsky
2019-08-04  1:41           ` Eric Abrahamsen
2019-08-04  1:09       ` Michael Heerdegen
2019-08-04  2:10         ` Eric Abrahamsen
2019-08-04  2:35           ` Eric Abrahamsen
2019-08-07 17:59             ` Lars Ingebrigtsen
2019-08-07 20:22               ` Eric Abrahamsen
2019-08-11 23:34                 ` Lars Ingebrigtsen
2019-08-12 15:24                   ` Eric Abrahamsen
2019-09-14 15:04                     ` Lars Ingebrigtsen
2019-09-15  0:27                       ` Eric Abrahamsen
2019-09-15 12:20                         ` Lars Ingebrigtsen
2019-09-15 23:31                           ` Eric Abrahamsen
2019-09-16 13:24                             ` Lars Ingebrigtsen
2019-09-16 22:37                               ` Eric Abrahamsen
2019-09-19 17:39                                 ` Eric Abrahamsen
2019-09-21  8:40                                   ` Michael Albinus
2019-09-21 21:31                                     ` Eric Abrahamsen
2019-09-22  1:04                                       ` Michael Heerdegen
2019-09-22  2:36                                         ` Eric Abrahamsen
2019-09-22  8:02                                           ` Michael Albinus
2019-09-25  9:39                                         ` Michael Heerdegen
2019-09-25 16:30                                           ` Eric Abrahamsen
2019-10-01 23:27                                             ` Eric Abrahamsen
2019-10-02 12:36                                               ` Michael Albinus
2019-10-03 23:22                                                 ` Eric Abrahamsen
2019-10-04  8:24                                                   ` Michael Albinus [this message]
2019-10-04 16:59                                                     ` Eric Abrahamsen
2019-10-05  7:53                                                       ` Michael Albinus
2019-10-05 11:59                                                         ` Eric Abrahamsen
2019-10-08  8:52                                                           ` bug#37590: " Michael Heerdegen
2019-10-08 18:40                                                             ` bug#36903: " Eric Abrahamsen
2019-10-09 14:37                                                               ` Michael Heerdegen
2019-08-12 15:36                   ` Eric Abrahamsen
2019-08-12 18:30                     ` Lars 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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zhig6hq1.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=36903@debbugs.gnu.org \
    --cc=eric@ericabrahamsen.net \
    --cc=michael_heerdegen@web.de \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).