ccing lsarc-ext at sun.com as a reply
Lubos Kosco wrote:
> Margot Miller wrote:
>
>> Minor issues:
>>
>> Uncommitted is more consistent with other ARC cases for package name
>>
>> SUNWopengrok Committed Package name
>>
>>
>
> will change ( I registered the
Margot Miller wrote:
> Minor issues:
>
> Uncommitted is more consistent with other ARC cases for package name
>
> SUNWopengrok Committed Package name
>
will change ( I registered the name hence I made it committed ;) )
>
> Attributes section needed in man page.
>
One thing I just noticed, is that the opengrok wrapper is listed with
a interface stability of "Committed". I am not sure that makes sense
for an example script. I would expect anyone using this script to
probably modify it and would definitely copy it to someplace else. I
would think that the
Hey Brian,
I would be happy with either uncommitted or volatile.
Thanks
Margot
On 03/23/09 11:55, Brian Utterback wrote:
> One thing I just noticed, is that the opengrok wrapper is listed with
> a interface stability of "Committed". I am not sure that makes sense
> for an example script. I wou
Thanks Lubos. I am fine with the networking answer.
The only other thing is to put an attributes section in the
man page.
I have no other issues.
+1 from me.
Margot
On 03/23/09 11:45, Lubos Kosco wrote:
> Margot Miller wrote:
>
>> Minor issues:
>>
>> Uncommitted is more consistent with ot
Lubos Kosco wrote:
> Margot Miller wrote:
>> Minor issues:
>>
>> Uncommitted is more consistent with other ARC cases for package name
>>
>> SUNWopengrok Committed Package name
>>
>
> will change ( I registered the name hence I made it committed ;) )
All package na
Resending to lsarc-ext.
Margot Miller wrote:
>
> Minor issues:
>
> Uncommitted is more consistent with other ARC cases for package name
>
> SUNWopengrokCommittedPackage name
>
>
> Attributes section needed in man page.
>
>
> And, could you elaborate more on this from the check
Minor issues:
Uncommitted is more consistent with other ARC cases for package name
SUNWopengrokCommitted Package name
Attributes section needed in man page.
And, could you elaborate more on this from the checklist:
3.4.6 General Security Question
Brian,
Please don't close this yet until we get a "+1" from someone.
I am reviewing it now.
Thanks
Margot
Brian Utterback wrote:
> The timer has expired and I didn't hear any objections, so I am
> marking this as closed, approved.
>
> Brian Utterback wrote:
>> Okay, any other comments? The tim
The timer has expired and I didn't hear any objections, so I am
marking this as closed, approved.
Brian Utterback wrote:
> Okay, any other comments? The timer has expired and I am inclined to
> close this as approved. Anyone?
>
> Lubos Kosco wrote:
>>
>>
>>
>>
>> On Mar 12, 2009, at 6:37 PM, Da
Okay, any other comments? The timer has expired and I am inclined to
close this as approved. Anyone?
Lubos Kosco wrote:
>
>
>
>
> On Mar 12, 2009, at 6:37 PM, Darren J Moffat wrote:
>
>> Brian Utterback wrote:
>>> I am sponsoring the enclosed fast track for Lubos Kosco. The timer is
>>> se
On Mar 12, 2009, at 6:37 PM, Darren J Moffat
wrote:
> Brian Utterback wrote:
>> I am sponsoring the enclosed fast track for Lubos Kosco. The timer
>> is set to March 17th. Proposal, checklist and man page are
>> enclosed for review.
>> This project requires the installation of Exuberen
Brian Utterback wrote:
> I am sponsoring the enclosed fast track for Lubos Kosco. The timer is
> set to March 17th. Proposal, checklist and man page are enclosed for
> review.
>
> This project requires the installation of Exuberent CTags, LSARC case
> 2008/741. The man page provided is not actu
I am sponsoring the enclosed fast track for Lubos Kosco. The timer is
set to March 17th. Proposal, checklist and man page are enclosed for
review.
This project requires the installation of Exuberent CTags, LSARC case
2008/741. The man page provided is not actually for a command called
opengrok
14 matches
Mail list logo
