all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 29489@debbugs.gnu.org
Subject: bug#29489: Obsolete gnus-remove-if and gnus-remove-if-not
Date: Sat, 02 Dec 2017 10:50:24 -0800	[thread overview]
Message-ID: <878telj767.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87lgilkg6b.fsf@users.sourceforge.net> (Noam Postavsky's message of "Fri, 01 Dec 2017 21:38:20 -0500")


On 12/01/17 21:38 PM, Noam Postavsky wrote:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> -			       (gnus-gethash group gnus-killed-hashtb)))
>> +			       (gethash group gnus-killed-hashtb)))
>
> Is this from a future patch?  As far as I can tell, you haven't changed
> gnus-killed-hashtb to a hashtable yet, it's still an obarray.

Bah! I'm sorry you've had to wade through my dumb mistakes. I'll make
better use of branches to keep these things separated cleanly.

Do you see anything else obviously wrong with this? I'll spend some more
time testing it, as well.

Eric





  reply	other threads:[~2017-12-02 18:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-28 17:02 bug#29489: Obsolete gnus-remove-if and gnus-remove-if-not Eric Abrahamsen
2017-11-28 17:23 ` John Wiegley
2017-11-28 18:01   ` Eric Abrahamsen
2017-11-28 23:44 ` Noam Postavsky
2017-11-29  0:07   ` Eric Abrahamsen
2017-11-29  0:40     ` Noam Postavsky
2017-11-29  1:42       ` Eric Abrahamsen
2017-11-29  2:36         ` Noam Postavsky
2017-11-29  3:31           ` Eric Abrahamsen
2017-11-30 18:29             ` Eric Abrahamsen
2017-12-02  2:38               ` Noam Postavsky
2017-12-02 18:50                 ` Eric Abrahamsen [this message]
2017-12-02 18:54                   ` Noam Postavsky
2017-12-02 18:53                     ` 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=878telj767.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=29489@debbugs.gnu.org \
    --cc=npostavs@users.sourceforge.net \
    /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.