From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Tadeus Prastowo <tadeus.prastowo@unitn.it>
Cc: Andy Moreton <andrewjmoreton@gmail.com>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: Proposed changes to gnus-dup.el
Date: Mon, 25 Mar 2019 18:14:01 +0000 [thread overview]
Message-ID: <874l7qrfdi.fsf@tcd.ie> (raw)
In-Reply-To: <CAN-HRFYS0B0H=ZMGHdGdSBCKL0+Wxnq52tV-Ld1MGbR2RXp6YQ@mail.gmail.com> (Tadeus Prastowo's message of "Mon, 25 Mar 2019 18:55:30 +0100")
Tadeus Prastowo <tadeus.prastowo@unitn.it> writes:
> On Mon, Mar 25, 2019 at 6:34 PM Basil L. Contovounesios <contovob@tcd.ie> wrote:
>> Sweeping changes across the whole Gnus system, OTOH, are far more risky,
>> as the recent switch to hash-tables has taught us.
>
> Would you mind giving me the URL(s) to the thread(s) that contain(s)
> the lesson, please?
See bugs 33653, 34973, 34974, 34981, 34983, and 34987.
https://debbugs.gnu.org/33653
https://debbugs.gnu.org/34973
https://debbugs.gnu.org/34974
https://debbugs.gnu.org/34981
https://debbugs.gnu.org/34983
https://debbugs.gnu.org/34987
--
Basil
next prev parent reply other threads:[~2019-03-25 18:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 3:55 Proposed changes to gnus-dup.el Basil L. Contovounesios
2019-03-25 15:59 ` Andy Moreton
2019-03-25 16:50 ` Stefan Monnier
2019-03-25 17:33 ` Basil L. Contovounesios
2019-03-27 17:57 ` Andy Moreton
2019-03-27 18:42 ` Stefan Monnier
2019-03-31 21:47 ` Basil L. Contovounesios
2019-03-25 17:33 ` Basil L. Contovounesios
2019-03-25 17:55 ` Tadeus Prastowo
2019-03-25 18:13 ` Eric Abrahamsen
2019-03-25 18:14 ` Basil L. Contovounesios [this message]
2019-03-25 17:42 ` Lars Ingebrigtsen
2019-03-25 18:13 ` Basil L. Contovounesios
2019-03-25 18:15 ` Eric Abrahamsen
2019-03-25 18:27 ` Basil L. Contovounesios
2019-04-01 23:43 ` Basil L. Contovounesios
2019-04-03 1:49 ` Eric Abrahamsen
2019-04-03 1:59 ` Basil L. Contovounesios
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=874l7qrfdi.fsf@tcd.ie \
--to=contovob@tcd.ie \
--cc=andrewjmoreton@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=tadeus.prastowo@unitn.it \
/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).