Re: Larger GC thresholds for non-interactive Emacs

[Eli Zaretskii]

> From: Ihor Radchenko <yantar92@gmail.com>
> Cc: owinebar@gmail.com,  larsi@gnus.org,  monnier@iro.umontreal.ca,
>   mattiase@acm.org,  theophilusx@gmail.com,  rms@gnu.org,  acm@muc.de,
>   emacs-devel@gnu.org
> Date: Thu, 23 Jun 2022 16:02:36 +0800
> 
> > And that won't help with past discussions whose commits are in the
> > tree for many years.
> 
> Can't the past discussions be directly updated by sending an extra email
> that links back to the new commit?

You mean, rely on search engines to find an addition to a discussion
made many years later?  My experience with searching the archives is
that it many times fails when the discussion crosses the year mark.
For starters, display of the archives by thread doesn't work in that
case as expected: you are given the illusion that the thread ends.

Searching the archives also has the disadvantage that in many cases
it's hard to know what are the keywords that would find the discussion
efficiently (i.e. without drowning it in thousands of irrelevant
messages).

Otherwise, I don't see how sending a message to a thread long dead
would help in this matter.  Am I missing something?

> > But yes, using such links is definitely helpful, and I'd encourage
> > people to use that more.  (That's one reason why changes should
> > preferably be discussed on the bug tracker: the bug number -- if not
> > forgotten to be mentioned in the log message -- serves as a pointer to
> > the discussions.)
> 
> What about the message ID? It should also be unique enough to link to
> the relevant ML thread. (it is a bit annoying that lists.gnu.org does
> not support easy search via link id, unlike e.g.
> 87r13n5muk.fsf@gnus.org/">https://yhetil.org/emacs-devel/87r13n5muk.fsf@gnus.org/).

That's okay, but is it really better than a URL of a message in the
archives?  It isn't much shorter.

The basic problem is to remember to mention a discussion, in any
form.  Even just a date and the name of the forum are usually enough
to quickly find the relevant thread.