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

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

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

Kévin Le Gouguec
Eli Zaretskii <[hidden email]> writes:

>> From: Lars Ingebrigtsen <[hidden email]>
>> Cc: Drew Adams <[hidden email]>,  [hidden email],
>>   [hidden email]
>> Date: Sat, 26 Sep 2020 17:45:21 +0200
>>
>> Good advice, but this reminds me of something that occurred to me some
>> time ago: Perhaps it would be nice if the script that sends out diff
>> emails also looked for text in the commit message that says "bug#4242"
>> and then Cc's [hidden email]?
>
> I don't think I want to get patches in my mailbox twice.  There's
> emacs-diffs for that purpose.

Maybe [hidden email]?

Quoth <https://debbugs.gnu.org/Developer.html>:

> If you wish to send a followup message which is not appropriate for
> any mailing list you can do so by sending it to
> [hidden email] or [hidden email]. Mail to
> [hidden email] is filed in the bug Tracking System but is
> not delivered to any individuals or mailing lists. Mail to
> [hidden email] is filed in the bug Tracking System and
> is delivered only to the maintainer of the package in question.



Reply | Threaded
Open this post in threaded view
|

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

Eli Zaretskii
> From: Kévin Le Gouguec <[hidden email]>
> Cc: Lars Ingebrigtsen <[hidden email]>,  [hidden email],
>   [hidden email]
> Date: Sat, 26 Sep 2020 20:58:38 +0200
>
> > I don't think I want to get patches in my mailbox twice.  There's
> > emacs-diffs for that purpose.
>
> Maybe [hidden email]?
>
> Quoth <https://debbugs.gnu.org/Developer.html>:
>
> > If you wish to send a followup message which is not appropriate for
> > any mailing list you can do so by sending it to
> > [hidden email] or [hidden email]. Mail to
> > [hidden email] is filed in the bug Tracking System but is
> > not delivered to any individuals or mailing lists. Mail to
> > [hidden email] 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?



Reply | Threaded
Open this post in threaded view
|

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

Lars Ingebrigtsen
Eli Zaretskii <[hidden email]> 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
>> > [hidden email] or [hidden email]. Mail to
>> > [hidden email] is filed in the bug Tracking System but is
>> > not delivered to any individuals or mailing lists. Mail to
>> > [hidden email] 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.

--
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



Reply | Threaded
Open this post in threaded view
|

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

Kévin Le Gouguec
Lars Ingebrigtsen <[hidden email]> writes:

> Eli Zaretskii <[hidden email]> 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
>>> > [hidden email] or [hidden email]. Mail to
>>> > [hidden email] is filed in the bug Tracking System but is
>>> > not delivered to any individuals or mailing lists. Mail to
>>> > [hidden email] 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.



Reply | Threaded
Open this post in threaded view
|

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

Lars Ingebrigtsen
Kévin Le Gouguec <[hidden email]> writes:

> 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.

It also helps the people who are looking at the web interface -- the
patch that resolves the bug report would be there, which I often find
helpful when looking at problems in other systems.

--
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



Reply | Threaded
Open this post in threaded view
|

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

Lars Ingebrigtsen
Dmitry Gutov <[hidden email]> writes:

> On 27.09.2020 15:17, Lars Ingebrigtsen wrote:
>> It also helps the people who are looking at the web interface -- the
>> patch that resolves the bug report would be there, which I often find
>> helpful when looking at problems in other systems.
>
> It could also be an HTTP URL instead of the patch itself, if we wanted
> to avoid duplication.

I'd prefer the patch itself -- systems come and go, and URLs don't last.

--
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no