From: Alex Legler <a3li@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: security@gentoo.org
Subject: Re: [gentoo-dev] Regarding long delays on GLSA generation
Date: Sat, 18 Jan 2014 17:02:19 +0100 [thread overview]
Message-ID: <52DAA58B.7060402@gentoo.org> (raw)
In-Reply-To: <1390059274.24148.80.camel@belkin5>
On 18.01.2014 16:34, Pacho Ramos wrote:
> Was looking to existing gedit bug reports and I found:
> https://bugs.gentoo.org/show_bug.cgi?id=257004
>
> That is only one more example of a really old bug report still opened
> and waiting for a GLSA. Was wondering what really causes this long
> delays, can't GLSA be done automatically?
Nope. But we do make constant refinements to speed up the process.
> Would a GLSA even have any
> sense for cases like this (after 5 years)
>
Yope. (I've answered this questions a trillion times by now, so care to
use $searchengine?)
> Thanks for your help
>
>
Not sure what you wanted to achieve by sending this email. Posting
$old_bug assigned to a specific team to -dev to point fingers at them is
just lame, as I'm pretty sure there's bug skeletons in every team's closet.
Appreciatively of your appreciation of our efforts,
Alex
--
Alex Legler <a3li@gentoo.org>
Gentoo Security/Ruby/Infrastructure
next prev parent reply other threads:[~2014-01-18 16:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-18 15:34 [gentoo-dev] Regarding long delays on GLSA generation Pacho Ramos
2014-01-18 16:02 ` Alex Legler [this message]
2014-01-18 16:30 ` Pacho Ramos
2014-01-18 16:33 ` Dirkjan Ochtman
2014-01-18 19:10 ` [gentoo-dev] " Duncan
2014-01-18 16:34 ` [gentoo-dev] " Pacho Ramos
2014-01-18 17:26 ` Alex Legler
2014-01-18 17:38 ` Pacho Ramos
2014-01-18 18:19 ` Alex Legler
2014-01-18 18:35 ` Pacho Ramos
2014-01-18 18:57 ` Pacho Ramos
-- strict thread matches above, loose matches on Subject: below --
2014-01-18 16:12 creffett
2014-01-18 18:57 Chris Reffett
[not found] <20140118185711.CFA13E0C62@pigeon.gentoo.org>
2014-01-18 19:08 ` Pacho Ramos
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52DAA58B.7060402@gentoo.org \
--to=a3li@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=security@gentoo.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox