[request-sponsor] Requesting sponsor for CR #6799167 (real gcc build fails in libshell) ...

2009-03-02 Thread John Beck
JohnS ... I was under the impression that code should JohnS never make reference to the bug it fixes. Am I mistaken here? No, you are quite correct. Referring to an open bug e.g.: /* * Work around silly misfeature until 699 is fixed. */ is OK, but the comment

[request-sponsor] Requesting sponsor for CR #6799167 (real gcc build fails in libshell) ...

2009-03-02 Thread Garrett D'Amore
John Sonnenschein wrote: Sorry to butt in here, but I was under the impression that code should never make reference to the bug it fixes. Am I mistaken here? Normally yes. However in this case, I think since the workaround may need some explanation, its not a bad idea to reference it.

[request-sponsor] request sponsor

2009-03-02 Thread Alan Coopersmith
For the benefit of potential sponsors, this is a suncluster/dssdk bug: 6603524 scds_get_child_mon_level() is dead code (Mentioning the bug synopsis when you request a sponsor helps us figure out if the bug is in an area we know enough to be a sponsor for.) VARUN raw wrote: hi, I am Varun from

[request-sponsor] [ksh93-integration-discuss] Requestingsponsor for CR #6799167 (real gcc build fails in libshell) ...

2009-03-02 Thread Roland Mainz
John Levon wrote: On Mon, Mar 02, 2009 at 11:01:54AM -0800, Garrett D'Amore wrote: John Sonnenschein wrote: Sorry to butt in here, but I was under the impression that code should never make reference to the bug it fixes. Am I mistaken here? Normally yes. However in this case, I think

[request-sponsor] sponsoring Varun to fix CR 6603524

2009-03-02 Thread Martin Rattner
Hello Varun, Thanks for your offer to contribute a fix for bug id 6603524. I will be pleased to sponsor your effort. FYI, I have updated the bug Description with the following additional information that might be helpful to you. I'm providing this info to you here because it hasn't shown