lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Thu, 29 May 2008 18:28:39 -0500
From:	Jon Tollefson <kniht@...ux.vnet.ibm.com>
To:	Martin Bligh <mbligh@...igh.org>
CC:	"Randy.Dunlap" <rdunlap@...otime.net>,
	"Rafael J. Wysocki" <rjw@...k.pl>, Theodore Tso <tytso@....edu>,
	Hugh Dickins <hugh@...itas.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Suresh Siddha <suresh.b.siddha@...el.com>,
	Venkatesh Pallipadi <venkatesh.pallipadi@...el.com>,
	bugme-admin@...ux-foundation.org
Subject: Re: [Bug #10732] REGRESSION: 2.6.26-rc2-git4: X server failed start
 on X61s laptop

Martin Bligh wrote:
> On Thu, May 29, 2008 at 2:15 PM, Randy.Dunlap <rdunlap@...otime.net> wrote:
>   
>> On Thu, 29 May 2008, Rafael J. Wysocki wrote:
>>
>>     
>>> On Tuesday, 27 of May 2008, Theodore Tso wrote:
>>>       
>>>> Bug #10732 is now closed.  BTW, it seems d*mned strange that the
>>>> submitter of the bug doesn't have the power to close a bug without
>>>> first grabbing the bug as the bug-fixer, changing its state to
>>>> ASSIGNED, and *then* being allowed to close the bug.  Grumble,
>>>> bugzilla's !#@#?@ process straightjacket....
>>>>         
>>> That depends on your account's access rights within the Bugzilla, which always
>>> have been a mystery to me.
>>>       
>> Martin Bligh should be able to clear that mystery up.
>>     
>
> Jon ... is that something we can configure? Seems ... wrong.
> Submitter and owner should both have power to edit the bug.
>   
Submitter and owner should be able to edit the bug as far I as can see.

If the bug is not already in the resolved state then you can use the
Close check box at the end of the 'Resolve' option line to close a bug
with one submit.  You do not have to change it to the assign state in
order to close it either - if it is the submitter or owner that is
closing it.  These statements do not apply to bugzilla in general but do
apply to the bugzilla.kernel.org one.

Jon

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ