On Wed, Jan 30, 2008 at 11:15:40PM +, 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
Ceri Does anyone else agree that this might be a problem...
Yes.
Ceri ... and are they able to see a way out?
For now, opensolaris-code is my best solution. Bigger picture,
I'm trying to push to get our tools et al. migrated so we can
move the gate outside the firewall and ultimately
Ceri Davies writes:
What I'm trying to achieve is to, at the very least, get Alice up to
a point where somebody might be interested in at least working with her
on getting a correct patch out so that a potential sponsor (who, let's
face it, have real jobs to do too) can be bothered to choose
On Fri, Feb 01, 2008 at 10:07:09AM -0500, James Carlson wrote:
Let's also take the whole sponsor question away, as that is a
temporary issue that's being fixed.
Sorry to sidetrack what is a very useful thread, but just how temporary
a problem is that likely to be? And how about the situation
Pete Bentley writes:
On Fri, Feb 01, 2008 at 10:07:09AM -0500, James Carlson wrote:
Let's also take the whole sponsor question away, as that is a
temporary issue that's being fixed.
Sorry to sidetrack what is a very useful thread, but just how temporary
a problem is that likely to be?
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
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
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
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
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,
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
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
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
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
14 matches
Mail list logo
