Thanks for the update, Garrett. Tables have been updated.
On 11/25/09 11:00 AM, Garrett D'Amore wrote:
> This is to record that Steve Stallion (OS0383) has contributed a fix for
> CR 6898794 (dnet interface lost "RUNNING" flag after "unplumb/plumb"
> cycle). I'm sponsoring his integration, and
This is to record that Steve Stallion (OS0383) has contributed a fix for
CR 6898794 (dnet interface lost "RUNNING" flag after "unplumb/plumb"
cycle). I'm sponsoring his integration, and I have already filed the
RTI. For those keeping track of sponsored integrations, this is one more.
- Ga
Hi,
FYI, Pradhap Devarajan agreed to take sponsor's responsibility for CRs
6687656 and 6662241 because I will be on longer vacation and these CRs
could be more active after ksh93 update 2 putback now.
Best regards,
Milan
Hi,
FYI, I will sponsor Danny.
Best regards,
Milan
danny webster p??e v so 18. 04. 2009 v 11:32 +0100:
> Hi,
>
> I'd like to request sponsorship for
>
> Bug ID 6344436
> Synopsis *mv* gives cryptic error when applied to unix domain sockets
> State 1-Dispatched (Default State)
> SCA: OS0243
>
Hi,
I'd like to request sponsorship for
Bug ID 6344436
Synopsis *mv* gives cryptic error when applied to unix domain sockets
State 1-Dispatched (Default State)
SCA: OS0243
User: dsw
I have working code already
thanks
dan.
I am sponsoring the following CR's for Roland Mainz:
6595183 RFE: Update ksh93-integration demo code
6561901 RFE: Add "shcomp" (shell script compiler) + kernel module to exec
binary
sh code
6451262 *sleep* RFE: /usr/bin/sleep should support floating-point values
6599668 RFE: Move consumers of al
hi, I mistakenly deleted the request for sponsorship so I would like
to state that I can sponsor Visakh (OS0192) for this RFE.
thanks, Jan.
--
Jan Pechanec
This is a newly-submitted bug and contains a very minor fix
pertaining to error messages in iscsitgtd. Looking for a sponsor and
a signed SCA is currently enroute to Linda B.
6477748: iscsitgt: Fix spelling and grammar nits in iscsitgtd error
messages
URL to cdiff patch is included in the
> Mike et al.,
>
> Well, perhaps nanofaq, cast into prose. From reading the web and lists I've
> seen, I'm still a little unclear on the actual modus operandi for us ex-
> officio engineers.
>
> I gather that the community buglist is world-readable--all bugs, save perhaps
> in the still-encumbere
Jim,
I'm not sure if this should stay on this list or not, but I thought it
was useful to have in the archive...
I've been planning to send a "guidelines" email to this list for several
days, and I'm still not quite there. Others will, no doubt, respond in
more detail to your questions, but I
Mike et al.,
Well, perhaps nanofaq, cast into prose. From reading the web and lists I've
seen, I'm still a little unclear on the actual modus operandi for us ex-officio
engineers.
I gather that the community buglist is world-readable--all bugs, save perhaps
in the still-encumbered components.
11 matches
Mail list logo