Michal Hlavinka wrote:
I'm getting the same mail for some time now for my critpath security
update. I'm just wondering how long it takes before update reaches
users
IMHO, the time it has taken so far is already too long. Stuff gets stuck in
the queue literally forever due to this stupid
On Thu, 2011-08-11 at 19:40 -0400, Doug Ledford wrote:
I've never got around to working up a coherent proposed modification and
submitting it, though - if anyone else can, that'd be great.
I'll just go back to what I've said before. I don't care what system
you create as long as there is
On 08/12/2011 10:28 AM, Adam Williamson wrote:
The reason why the package maintainer gets nagged has been explained
several times: part of the theory behind the current process is that it
is, to some extent, your responsibility as a package maintainer to
ensure your package gets tested. You
On 08/12/2011 09:40 AM, Kalev Lember wrote:
On 08/12/2011 10:28 AM, Adam Williamson wrote:
The reason why the package maintainer gets nagged has been explained
several times: part of the theory behind the current process is that it
is, to some extent, your responsibility as a package
On 08/10/2011 03:02 PM, Doug Ledford wrote:
Can we please either disable these nag messages or give developers the
ability to push a package regardless of testing when it reaches nag age?
I'm getting the same mail for some time now for my critpath security
update. I'm just wondering how long
On Thu, Aug 11, 2011 at 5:32 PM, Adam Williamson awill...@redhat.com wrote:
On Wed, 2011-08-10 at 09:02 -0400, Doug Ledford wrote:
Can we please either disable these nag messages or give developers the
ability to push a package regardless of testing when it reaches nag age?
You have that
On Fri, 2011-08-12 at 11:30 +0200, Michal Hlavinka wrote:
On 08/10/2011 03:02 PM, Doug Ledford wrote:
Can we please either disable these nag messages or give developers the
ability to push a package regardless of testing when it reaches nag age?
I'm getting the same mail for some time
On 8/12/2011 3:28 AM, Adam Williamson wrote:
On Thu, 2011-08-11 at 19:40 -0400, Doug Ledford wrote:
I've never got around to working up a coherent proposed modification and
submitting it, though - if anyone else can, that'd be great.
I'll just go back to what I've said before. I don't care
On Wed, 2011-08-10 at 09:02 -0400, Doug Ledford wrote:
Can we please either disable these nag messages or give developers the
ability to push a package regardless of testing when it reaches nag age?
You have that ability for non-critpath updates, but for critpath the
thought is that updates
On Wed, 2011-08-10 at 09:02 -0400, Doug Ledford wrote:
Can we please either disable these nag messages or give developers the
ability to push a package regardless of testing when it reaches nag age?
You have that ability for non-critpath updates, but for critpath the
thought is that updates
On 08/11/2011 12:32 PM, Adam Williamson wrote:
On Wed, 2011-08-10 at 09:02 -0400, Doug Ledford wrote:
Can we please either disable these nag messages or give developers the
ability to push a package regardless of testing when it reaches nag age?
You have that ability for non-critpath
11 matches
Mail list logo
