[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jdt-dev] Buffer overflow
|
voilà: https://bugs.eclipse.org/bugs/show_bug.cgi?id=563177
Stephan
On 14.05.20 18:33, Daniel Megert wrote:
That would be acceptable as well.
Stephan, can you open a bug report and share it here? You can mention the idea I
raised and also the one from Mickael.
Dani
From: Mickael Istria <mistria@xxxxxxxxxx>
To: "Eclipse JDT general developers list." <jdt-dev@xxxxxxxxxxx>
Date: 14.05.2020 18:23
Subject: [EXTERNAL] Re: [jdt-dev] Buffer overflow
Sent by: jdt-dev-bounces@xxxxxxxxxxx
--------------------------------------------------------------------------------
On Thu, May 14, 2020 at 6:13 PM Daniel Megert <_daniel_megert@xxxxxx.com_
<mailto:daniel_megert@xxxxxxxxxx>> wrote:
I am also not a fan of auto-closing but I like the idea to ping the author to
verify whether the bug is still relevant. I'm not sure whether the webmaster can
do this, but maybe we could add a comment, mark it stale (not in subject) and
only send a note to the author.
I imagine the same bot that does add a Bugzilla comment or change bug status
could be tweaked to directly send a mail to the author to ask them for
verification with comment or closing action, without directly touching the bug
(then avoiding notifications).
What do you think?_______________________________________________
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jdt-dev
_______________________________________________
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jdt-dev
