[request-sponsor] Fwd: [Fwd: Fix for bug-6561465]
} }We have a fix for the bug 6561465. We are attacing the diff file } }regards }Abhilash-oso183 }Arjun-oso211 } } } } }Abhilash wrote: }Sir, } }I abhilash and arjun, Students of amrita university would lioke to work on the }bug 6561465 . My sca number is oso183 and arjuns is oso211. }The synopsis is }The file /usr/lib/help/auths/locale/C/SmfAutofsStates.html has a typo. }The text says Authorizations Include and should say Authorizations }Included. }Looking at file in smc and the reason is obvious. } } }Abhilash }Arjun } } -- Sun Microsystems - India Engineering Centre http://blogs.sun.com/jkini -- next part -- Fix is good. Please send a mailto request-sponsor with the fix. ~Kini On Wed, 30 Jan 2008 10:31 -, manjula pc - Sun Microsystems - Bangalore...: } } } Original Message }Subject: Fix for bug-6561465 }Date: Tue, 29 Jan 2008 11:56:44 +0530 (IST) }From: Abhilash abhilash_05cse01 at students.amrita.ac.in }To:manjula pc - Sun Microsystems - Bangalore India Manjula.Pc at Sun.COM } } } }Ma'am } }We have a fix for the bug 6561465. We are attacing the diff file } }regards }Abhilash-oso183 }Arjun-oso211 } } } } }Abhilash wrote: }Sir, } }I abhilash and arjun, Students of amrita university would lioke to work on the }bug 6561465 . My sca number is oso183 and arjuns is oso211. }The synopsis is }The file /usr/lib/help/auths/locale/C/SmfAutofsStates.html has a typo. }The text says Authorizations Include and should say Authorizations }Included. }Looking at file in smc and the reason is obvious. } } }Abhilash }Arjun } } -- Sun Microsystems - India Engineering Centre http://blogs.sun.com/jkini -- next part -- An embedded and charset-unspecified text was scrubbed... Name: diff_SmfAutofsStates.txt URL: http://mail.opensolaris.org/pipermail/request-sponsor/attachments/20080131/dc697ea4/attachment.txt
[request-sponsor] BUGS : 6561458 4882712 4301328 4149285 6313275 6313279 4964217
On Thu, 31 Jan 2008, Avinash Joshi wrote: == Bug ID 4964217 Synopsis ssh -v code needs spell checking - successfull != successful Category:Subcategory ssh:other that one was already fixed, closing the bug now. It might be a good idea to check that the bug you want is still a bug and if not, report it. thanks, Jan. -- Jan Pechanec
[request-sponsor] Shooting my mouth off
Ceri Davies writes: It occurs to me that I've been reviewing patches posted here where it might not actually be welcome. Tell me to shut up if necessary, although I'm concerned that this review should happen and preferably in good time after a submission is posted (rather than after the potentially long wait for a sponsor to come forward). I'd much rather see request-sponsor used just for requesting a sponsor and not for submitting patches or for reviews. Yes, all changes need thorough review, and comments should always be welcome, but this just isn't the right forum for it. Not everyone who should be looking at the proposed changes (or the review comments themselves) is actually on this list. Seeing those submitters go to the relevant community or project mailing list with a proposed patch (or better yet a pointer to a webrev) would be greatly preferred, and if we can gently guide them there when they mistakenly post changes here, that'd be good. -- James Carlson, Solaris Networking james.d.carlson at sun.com Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
[request-sponsor] Bug Fix for 6589063 - diff file attached
Hi I will sponsor this bug fix for you. Please contact me directly from here onwards. Regards Viswa x27649 Vidyalakshmi wrote: Hi, We are Deepthi Devaki A R(SCA No. OS0172 ) and R Vidya Lakshmi ( OS0171 ). We are attaching the diff file for the bug 6589063. We request a sponsor for the fix. Bug ID 6589063 Synopsis typo in 'possiblely' in pkcs#11 kernel/soft token Category:Subcategory solaris-crypto:pkcs11 Keywords ef-reviewed Thanks Regards Deepthi Devaki A R R Vidya Lakshmi Amrita University ___ request-sponsor mailing list request-sponsor at opensolaris.org
[request-sponsor] Shooting my mouth off
On Thu, 31 Jan 2008, Avinash Joshi wrote: But how do we do a webrev? I got the workspace at cr.opensolaris.org/~avinashj The manpage - usr/src/tools/scripts/webrev.1 - explains what you can do with it. Basically, you need to keep an unmodified ON sourcetree, take a clone of that, modify your files there, and then run webrev. FrankH. Thanks regards, Avinash Joshi On 1/31/08, Frank.Hofmann at sun.com Frank.Hofmann at sun.com wrote: On Thu, 31 Jan 2008, Antonello Cruz wrote: James Carlson wrote: Seeing those submitters go to the relevant community or project mailing list with a proposed patch (or better yet a pointer to a webrev) would be greatly preferred, and if we can gently guide them there when they mistakenly post changes here, that'd be good. Quick question: Do the contributors have access to the tools to generate webrevs? If you've got a full opensolaris source tree, you'll find it in: usr/src/tools/scripts/webrev.sh FrankH. ___ request-sponsor mailing list request-sponsor at opensolaris.org -- Sent from Gmail for mobile | mobile.google.com Thanks Regards, Avinash Joshi AM106IT015 Department of Information Technology Amrita School of Engineering Amrita Vishwa Vidyapeetham Amritapuri Campus Clappana P.O., Kollam 690 525 Kerala, INDIA Ph : (+91) 98954 94427 Blog: http://avinashtjoshi.wordpress.com/ Site: http://avinashtjoshi.googlepages.com/ -- No good can come from selling your freedom, not for all the gold in the world, for the value of this heavenly gift far exceeds that of any fortune on earth. --
[request-sponsor] Shooting my mouth off
Avinash, Have a look at usr/src/tools/README.tools After building the tools, go the the top of your workspace (I don't think it will work on cr.opensolaris.org/~avinashj you'll have to do it locally) and run 'ws' to set the environment. Then run wx webrev. However, for it to work, you'll have to properly checkout the files you want to edit with wx edit files to edit You can ask me further questions off the list if you need so. Antonello Avinash Joshi wrote: But how do we do a webrev? I got the workspace at cr.opensolaris.org/~avinashj Thanks regards, Avinash Joshi On 1/31/08, Frank.Hofmann at sun.com Frank.Hofmann at sun.com wrote: On Thu, 31 Jan 2008, Antonello Cruz wrote: James Carlson wrote: Seeing those submitters go to the relevant community or project mailing list with a proposed patch (or better yet a pointer to a webrev) would be greatly preferred, and if we can gently guide them there when they mistakenly post changes here, that'd be good. Quick question: Do the contributors have access to the tools to generate webrevs? If you've got a full opensolaris source tree, you'll find it in: usr/src/tools/scripts/webrev.sh FrankH. ___ request-sponsor mailing list request-sponsor at opensolaris.org
[request-sponsor] Fwd: Shooting my mouth off
Doh. Missed reply-all. -- Forwarded message -- From: Mark Martin storycraf...@gmail.com Date: Jan 30, 2008 6:27 PM Subject: Re: [request-sponsor] Shooting my mouth off To: Ceri Davies ceri at submonkey.net On Jan 30, 2008 5:15 PM, Ceri Davies ceri at submonkey.net wrote: It occurs to me that I've been reviewing patches posted here where it might not actually be welcome. Tell me to shut up if necessary, although I'm concerned that this review should happen and preferably in good time after a submission is posted (rather than after the potentially long wait for a sponsor to come forward). I'm glad you mentioned this because honestly I've been tempted to say something for quite some time. Personally, I don't understand why the code reviews aren't being done in a more appropriate group or project forum -- one matching the project that the bug is categorized in or even a (non-existent) code-reviews-discuss. I've personally viewed this forum as spammed with patches and mini-reviews, and although I lament the situation, I'm not sufficiently irked enough to want to police it myself. I've just thrown some filters at the irritation, gotten over my idealogical angst, assumed I was the only one so bothered, and moved on. Please don't take this as a shut-up. Just so I don't sound like a nit-ninny, I suppose I could offer for consideration a possible solution[1] : - create a new discussion form where _all_ code-reviews are conducted, - hijack code-discuss for this purpose, or - steer people towards the appropriate forum (according to bug categorization). Mark [1] Assuming that I was the only one who thought there was even a problem.
[request-sponsor] Shooting my mouth off
Antonello Cruz writes: After building the tools, go the the top of your workspace (I don't think it will work on cr.opensolaris.org/~avinashj you'll have to do it locally) and run 'ws' to set the environment. Then run wx webrev. However, for it to work, you'll have to properly checkout the files you want to edit with wx edit files to edit wx edit seems fairly unlikely for an external (non-SWAN) user who doesn't have teamware access. Instead, you'll want to pull the hg-enabled tools from the SCM Migration web site: http://www.opensolaris.org/os/project/scm-migration/ (Look for downloads on that page.) Those packages will install the necessary tools in /opt/onbld. You can then run hgsetup to set up your $HOME/.hgrc file to work with the tools, and webrev will work as expected. When you're ready for review, just scp -r that webrev directory out to some web site (such as cr.opensolaris.org). -- James Carlson, Solaris Networking james.d.carlson at sun.com Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
[request-sponsor] Shooting my mouth off
Antonello Cruz wrote: Avinash, Have a look at usr/src/tools/README.tools After building the tools, go the the top of your workspace (I don't think it will work on cr.opensolaris.org/~avinashj you'll have to do it locally) and run 'ws' to set the environment. Then run wx webrev. However, for it to work, you'll have to properly checkout the files you want to edit with wx edit files to edit You can ask me further questions off the list if you need so. So where do we discuss how to help everyone trying to help? I.e., others might have questions and watching your exchange can help. I know I looked for some help on webrev to send to a contributer and couldn't find any right off the bat.
[request-sponsor] Shooting my mouth off
James Carlson wrote: wx edit seems fairly unlikely for an external (non-SWAN) user who doesn't have teamware access. Instead, you'll want to pull the hg-enabled tools from the SCM Migration web site: http://www.opensolaris.org/os/project/scm-migration/ Just because I hit this problem with a contributer and because at least one person had problems with Mercurial, I put together a blog entry that shows you how to use webrev to get a code review: http://blogs.sun.com/tdh/entry/getting_a_webrev_generated_for
[request-sponsor] Shooting my mouth off
acruz == Antonello Cruz Antonello.Cruz at sun.com writes: acruz Quick question: Do the contributors have access to the tools to acruz generate webrevs? Yes, though the tools from the SCM Migration project[1] are likely to work better than what's in the gate, especially with respect to webrev and Mercurial. mike [1] http://www.opensolaris.org/os/project/scm-migration/
