bug#43569: 28.0.50; Menu "Continue Tags Search" signals an error

[Kévin Le Gouguec]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> > If you wish to send a followup message which is not appropriate for
>>> > any mailing list you can do so by sending it to
>>> > nnn-quiet@debbugs.gnu.org or nnn-maintonly@debbugs.gnu.org. Mail to
>>> > nnn-quiet@debbugs.gnu.org is filed in the bug Tracking System but is
>>> > not delivered to any individuals or mailing lists. Mail to
>>> > nnn-maintonly@debbugs.gnu.org is filed in the bug Tracking System and
>>> > is delivered only to the maintainer of the package in question.
>>
>> That sounds like the direct opposite of what is being saiught here,
>> doesn't it?
>
> It doesn't help with sending the patch to the bug reporter, but it does
> fix the problem of stashing a copy of the patch in the bug tracker (and
> not annoying anybody when doing so), though.

Yes, that's the issue I was thinking about (sorry for not being explicit
enough, I counted on my selective quoting to do the work for me).

FWIW this feature (having the BTS record what patches were applied in
the context of a specific report) is a thing other forges do.

I can't speak for the maintainers of projects hosted on these forges,
but I can imagine it being handy: sure, finding all commits referencing
a bug ID is "just one Git command away", but that can mean a couple of
seconds twiddling one's thumbs while the disk spins; having that
information readily displayed in the thread sounds like a timesaver.