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
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 wrote:
> On Thu, 31 Jan 2008, Antonello Cruz wrote:
>
> > James Carlson wrote:
> >> Seeing those submitters go to the relevant community or project
Hi,
V ne, 27. 01. 2008 v 16:52, Marco van Wieringen p??e:
> Hi,
>
> I would like to request an sponsor for BUG 6655471 regarding debugging
> output from LDAP client lib even when build in non-debug mode.
>
> My SCA nr is : OS0231
>
OK, so we reached some agreement where to move this CR and im
ris.org/pipermail/request-sponsor/attachments/20080131/c64ecba0/attachment.bin>
ris.org/pipermail/request-sponsor/attachments/20080131/93f8c6d4/attachment.bin>
Hi
I am Avinash Joshi. I would like to work on the following bugs. My SCA
number is OS0142. I am requesting a sponsor for these many bugs now as
I have my exams starting on Monday. I will start working on all the
bugs from Wednesday i.e., 6th of Feb.
The first two bugs have a responsible engineer
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 you
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 mistake
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 t
I'll sponsor this.
mike
Tom Haynes writes:
> But, I'd like a forum for people to suggest patches, ask for reviews,
> etc.
The best place to do that is in a relevant community or project.
That's where the expertise in that technical area is gathered.
> Instead of
> the exchanges being scattered over different communitie
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 t
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
James Carlson wrote:
> 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
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. Ho
Doh. Missed reply-all.
-- Forwarded message --
From: Mark Martin
Date: Jan 30, 2008 6:27 PM
Subject: Re: [request-sponsor] Shooting my mouth off
To: Ceri Davies
On Jan 30, 2008 5:15 PM, Ceri Davies wrote:
> It occurs to me that I've been reviewing patches posted here where it
> "acruz" == Antonello Cruz 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.
mik
States.txt
URL:
<http://mail.opensolaris.org/pipermail/request-sponsor/attachments/20080131/dc697ea4/attachment.txt>
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
>
James Carlson wrote:
> 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 h
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 t
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 quest
Ceri Davies 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
23 matches
Mail list logo
