Re: [request-sponsor] Re: [osol-discuss] 1 new request-sponsor putback: 39 total

2006-03-08 Thread Karyn Ritter
[Apologies if this has already been responded to... I'm catching up.] The code for bugs.opensolaris.org (and bugs.sun.com) are not sophisticated enough to be able to do this. The application we use currently shares the same code base as bugs.sun.com. Because Suggested Fix often contains code t

Re: [request-sponsor] Re: [osol-discuss] 1 new request-sponsor putback: 39 total

2006-03-03 Thread Valerie Anne Bubb
On Thu, 2 Mar 2006, Artem Kachitchkine wrote: How would it determine which bugs those fields can be exported for? We can't do it for all bugs, since some contain source which cannot be disclosed publically. It's not an unsolvable problem. E.g. there could be a special field accessible only

Re: [request-sponsor] Re: [osol-discuss] 1 new request-sponsor putback: 39 total

2006-03-02 Thread Chandan B.N.
On Thu, 2006-03-02 at 20:23 +0100, Felix Schulte wrote: > > > Jim, could you please post the patch diffs (diff -u), too? That may be > > > helpful to see what changed exactly. Once a SCM is in place this transient problem should go away. till then, (when the code is synced) you can search for the

Re: [request-sponsor] Re: [osol-discuss] 1 new request-sponsor putback: 39 total

2006-03-02 Thread Dan Price
On Thu 02 Mar 2006 at 11:33AM, Alan Coopersmith wrote: > Artem Kachitchkine wrote: > > > >>It would be cool if the diffs would be part of the announcements. > > > > > >The diffs are always attached to the bug ID in the bug database. They > >don't appear on the bugs.opensolarig.org though. I don't

Re: [request-sponsor] Re: [osol-discuss] 1 new request-sponsor putback: 39 total

2006-03-02 Thread Artem Kachitchkine
How would it determine which bugs those fields can be exported for? We can't do it for all bugs, since some contain source which cannot be disclosed publically. It's not an unsolvable problem. E.g. there could be a special field accessible only from Sun, that the sponsor would set. -Artem.

Re: [request-sponsor] Re: [osol-discuss] 1 new request-sponsor putback: 39 total

2006-03-02 Thread Alan Coopersmith
Artem Kachitchkine wrote: It would be cool if the diffs would be part of the announcements. The diffs are always attached to the bug ID in the bug database. They don't appear on the bugs.opensolarig.org though. I don't see why they shouldn't for contributed patches, perhaps it's just a tec

Re: [request-sponsor] Re: [osol-discuss] 1 new request-sponsor putback: 39 total

2006-03-02 Thread Artem Kachitchkine
It would be cool if the diffs would be part of the announcements. The diffs are always attached to the bug ID in the bug database. They don't appear on the bugs.opensolarig.org though. I don't see why they shouldn't for contributed patches, perhaps it's just a technical problem with databas

Re: [request-sponsor] Re: [osol-discuss] 1 new request-sponsor putback: 39 total

2006-03-02 Thread Felix Schulte
On 3/2/06, Jim Grisanzio <[EMAIL PROTECTED]> wrote: > Felix Schulte wrote: > > On 3/2/06, Jim Grisanzio <[EMAIL PROTECTED]> wrote: > > > >>Thanks to Juergen Keil for this bug fix below and to Minskey Guo for > >>sponsoring the fix through to putback: > >> > >>Putback #39 > >>ID: 6388096 > >>Desc: N

Re: [request-sponsor] Re: [osol-discuss] 1 new request-sponsor putback: 39 total

2006-03-02 Thread Jim Grisanzio
Felix Schulte wrote: On 3/2/06, Jim Grisanzio <[EMAIL PROTECTED]> wrote: Thanks to Juergen Keil for this bug fix below and to Minskey Guo for sponsoring the fix through to putback: Putback #39 ID: 6388096 Desc: NULL pointer dereference panic in sd_range_lock() Submitted by Juergen Keil on 2/21