From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: cohen@bu.edu, 37871@debbugs.gnu.org
Subject: bug#37871: 27.0.50; Merge feature/gnus-select2
Date: Fri, 04 Sep 2020 18:31:21 -0700 [thread overview]
Message-ID: <87a6y5ggba.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <874kq2bvun.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Sun, 19 Jul 2020 22:26:24 -0700")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>
>>>> Sounds great. Merge away. :-)
>>>
>>> Andy, do you want to do the honors?
>>
>> This was in October 2019, and nnselect.el doesn't seem to exist yet.
>> :-) Somebody should get mergin'.
>
> It's possible Andy was waiting for me to finish my *-retrieve-headers
> patch, allowing backends to return headers directly, before he merged
> nnselect, as that patch affects how that backend works. Either way, I
> really need to take half a day and finish that patch (it's delicate, and
> needs some consideration). And Andy should be the one to do the nnselect
> merge.
And it's in!
Lars, what do you think about bumping the Gnus version number for big
changes like this? If only to make bug triage easier. In retrospect I
wish I'd done this for the obarray->hashtable change.
next prev parent reply other threads:[~2020-09-05 1:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 16:14 bug#37871: 27.0.50; Merge feature/gnus-select2 Eric Abrahamsen
2019-10-22 18:13 ` Lars Ingebrigtsen
2019-10-22 18:26 ` Eric Abrahamsen
2019-10-22 18:31 ` Lars Ingebrigtsen
2019-10-22 19:39 ` Eric Abrahamsen
2020-07-19 15:35 ` Lars Ingebrigtsen
2020-07-20 5:26 ` Eric Abrahamsen
2020-09-05 1:31 ` Eric Abrahamsen [this message]
2020-09-05 12:58 ` Lars Ingebrigtsen
2020-09-05 15:44 ` Eric Abrahamsen
2020-09-06 15:33 ` Basil L. Contovounesios
2020-09-06 22:53 ` Andrew Cohen
2020-10-15 16:04 ` 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=87a6y5ggba.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=37871@debbugs.gnu.org \
--cc=cohen@bu.edu \
--cc=larsi@gnus.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.
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.