You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by bu...@locus.apache.org on 2000/04/05 22:16:57 UTC
[Bug 26] Changed - Irix locking problems
http://www.apache.org/bugs/show_bug.cgi?id=26
*** shadow/26 Wed Apr 5 11:02:04 2000
--- shadow/26.tmp.70062 Wed Apr 5 13:16:57 2000
***************
*** 3,9 ****
Version: 2.0a
Platform: SGI
OS/Version: IRIX
! Status: RESOLVED
Resolution: FIXED
Severity: serious
Priority: medium
--- 3,9 ----
Version: 2.0a
Platform: SGI
OS/Version: IRIX
! Status: REOPENED
Resolution: FIXED
Severity: serious
Priority: medium
Re: [Bug 26] Changed - Irix locking problems
Posted by rb...@apache.org.
On Wed, 5 Apr 2000 rbb@apache.org wrote:
>
> > > Can I ask why this bug report was re-opened? As far as I can see the vast
> > > majority of this patch was applied to CVS.
> > >
> > > This brings up an interesting point, does anybody know how to setup
> > > bugzilla so that when a new account is created that user doesn't have
> > > rights to edit bug reports?
> >
> > Hmm. Am I missing something, or does bugzilla do no tracking of state
> > changes or who made the state change? That seems... crazy.
>
> State changes, it looks like those are tracked, but not who changed the
> state, which does seem a bit nuts to me too.
I'm wrong. Sorry. If you click on "View Bug Activity" you can see who
changed the state.
I wish this was more obvious, but at least its there.
Ryan
_______________________________________________________________________________
Ryan Bloom rbb@apache.org
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------
Re: [Bug 26] Changed - Irix locking problems
Posted by rb...@apache.org.
On Wed, 5 Apr 2000 rbb@apache.org wrote:
>
> > > Can I ask why this bug report was re-opened? As far as I can see the vast
> > > majority of this patch was applied to CVS.
> > >
> > > This brings up an interesting point, does anybody know how to setup
> > > bugzilla so that when a new account is created that user doesn't have
> > > rights to edit bug reports?
> >
> > Hmm. Am I missing something, or does bugzilla do no tracking of state
> > changes or who made the state change? That seems... crazy.
>
> State changes, it looks like those are tracked, but not who changed the
> state, which does seem a bit nuts to me too.
I'm wrong. Sorry. If you click on "View Bug Activity" you can see who
changed the state.
I wish this was more obvious, but at least its there.
Ryan
_______________________________________________________________________________
Ryan Bloom rbb@apache.org
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------
Re: [Bug 26] Changed - Irix locking problems
Posted by rb...@apache.org.
> > Can I ask why this bug report was re-opened? As far as I can see the vast
> > majority of this patch was applied to CVS.
> >
> > This brings up an interesting point, does anybody know how to setup
> > bugzilla so that when a new account is created that user doesn't have
> > rights to edit bug reports?
>
> Hmm. Am I missing something, or does bugzilla do no tracking of state
> changes or who made the state change? That seems... crazy.
State changes, it looks like those are tracked, but not who changed the
state, which does seem a bit nuts to me too.
Ryan
_______________________________________________________________________________
Ryan Bloom rbb@apache.org
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------
Re: [Bug 26] Changed - Irix locking problems
Posted by rb...@apache.org.
> > Can I ask why this bug report was re-opened? As far as I can see the vast
> > majority of this patch was applied to CVS.
> >
> > This brings up an interesting point, does anybody know how to setup
> > bugzilla so that when a new account is created that user doesn't have
> > rights to edit bug reports?
>
> Hmm. Am I missing something, or does bugzilla do no tracking of state
> changes or who made the state change? That seems... crazy.
State changes, it looks like those are tracked, but not who changed the
state, which does seem a bit nuts to me too.
Ryan
_______________________________________________________________________________
Ryan Bloom rbb@apache.org
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------
Re: [Bug 26] Changed - Irix locking problems
Posted by Marc Slemko <ma...@znep.com>.
On Wed, 5 Apr 2000 rbb@apache.org wrote:
> On 5 Apr 2000 bugzilla-daemon@locus.apache.org wrote:
>
> > http://www.apache.org/bugs/show_bug.cgi?id=26
> >
> > *** shadow/26 Wed Apr 5 11:02:04 2000
> > --- shadow/26.tmp.70062 Wed Apr 5 13:16:57 2000
> > ***************
> > *** 3,9 ****
> > Version: 2.0a
> > Platform: SGI
> > OS/Version: IRIX
> > ! Status: RESOLVED
> > Resolution: FIXED
> > Severity: serious
> > Priority: medium
> > --- 3,9 ----
> > Version: 2.0a
> > Platform: SGI
> > OS/Version: IRIX
> > ! Status: REOPENED
> > Resolution: FIXED
> > Severity: serious
> > Priority: medium
>
> Can I ask why this bug report was re-opened? As far as I can see the vast
> majority of this patch was applied to CVS.
>
> This brings up an interesting point, does anybody know how to setup
> bugzilla so that when a new account is created that user doesn't have
> rights to edit bug reports?
Hmm. Am I missing something, or does bugzilla do no tracking of state
changes or who made the state change? That seems... crazy.
Re: [Bug 26] Changed - Irix locking problems
Posted by Marc Slemko <ma...@znep.com>.
On Wed, 5 Apr 2000 rbb@apache.org wrote:
> On 5 Apr 2000 bugzilla-daemon@locus.apache.org wrote:
>
> > http://www.apache.org/bugs/show_bug.cgi?id=26
> >
> > *** shadow/26 Wed Apr 5 11:02:04 2000
> > --- shadow/26.tmp.70062 Wed Apr 5 13:16:57 2000
> > ***************
> > *** 3,9 ****
> > Version: 2.0a
> > Platform: SGI
> > OS/Version: IRIX
> > ! Status: RESOLVED
> > Resolution: FIXED
> > Severity: serious
> > Priority: medium
> > --- 3,9 ----
> > Version: 2.0a
> > Platform: SGI
> > OS/Version: IRIX
> > ! Status: REOPENED
> > Resolution: FIXED
> > Severity: serious
> > Priority: medium
>
> Can I ask why this bug report was re-opened? As far as I can see the vast
> majority of this patch was applied to CVS.
>
> This brings up an interesting point, does anybody know how to setup
> bugzilla so that when a new account is created that user doesn't have
> rights to edit bug reports?
Hmm. Am I missing something, or does bugzilla do no tracking of state
changes or who made the state change? That seems... crazy.
Re: [Bug 26] Changed - Irix locking problems
Posted by rb...@apache.org.
On 5 Apr 2000 bugzilla-daemon@locus.apache.org wrote:
> http://www.apache.org/bugs/show_bug.cgi?id=26
>
> *** shadow/26 Wed Apr 5 11:02:04 2000
> --- shadow/26.tmp.70062 Wed Apr 5 13:16:57 2000
> ***************
> *** 3,9 ****
> Version: 2.0a
> Platform: SGI
> OS/Version: IRIX
> ! Status: RESOLVED
> Resolution: FIXED
> Severity: serious
> Priority: medium
> --- 3,9 ----
> Version: 2.0a
> Platform: SGI
> OS/Version: IRIX
> ! Status: REOPENED
> Resolution: FIXED
> Severity: serious
> Priority: medium
Can I ask why this bug report was re-opened? As far as I can see the vast
majority of this patch was applied to CVS.
This brings up an interesting point, does anybody know how to setup
bugzilla so that when a new account is created that user doesn't have
rights to edit bug reports?
Ryan
_______________________________________________________________________________
Ryan Bloom rbb@apache.org
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------
Re: [Bug 26] Changed - Irix locking problems
Posted by rb...@apache.org.
On 5 Apr 2000 bugzilla-daemon@locus.apache.org wrote:
> http://www.apache.org/bugs/show_bug.cgi?id=26
>
> *** shadow/26 Wed Apr 5 11:02:04 2000
> --- shadow/26.tmp.70062 Wed Apr 5 13:16:57 2000
> ***************
> *** 3,9 ****
> Version: 2.0a
> Platform: SGI
> OS/Version: IRIX
> ! Status: RESOLVED
> Resolution: FIXED
> Severity: serious
> Priority: medium
> --- 3,9 ----
> Version: 2.0a
> Platform: SGI
> OS/Version: IRIX
> ! Status: REOPENED
> Resolution: FIXED
> Severity: serious
> Priority: medium
Can I ask why this bug report was re-opened? As far as I can see the vast
majority of this patch was applied to CVS.
This brings up an interesting point, does anybody know how to setup
bugzilla so that when a new account is created that user doesn't have
rights to edit bug reports?
Ryan
_______________________________________________________________________________
Ryan Bloom rbb@apache.org
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------