Mike Kupfer wrote:
"stevel" == Stephen Lau <[EMAIL PROTECTED]> writes:
stevel> The developer tools ... are within ON under
stevel> usr/src/tools/scripts. How do people want to do this? Should I
stevel> just create a clone of onnv-gate into a Mercurial repository
stevel> (scm-migration/devtools), and we can work within that?
I lean slightly towards that approach.
One reason is I think it will make merges easier in the event of
parallel changes.
I'm not anticipating a lot of parallel changes happening to these tools
in ON.
My worry is that making it a clone of onnv-gate brings in 30,000+ other
files we really have no interest in, given that the tools we *are*
interested in are fairly standalone.
Another reason is that there may be issues that we'll run into with the
larger workspace that we won't hit with a smaller one (with just the
tools).
Could you expand on this for me?
But I'm okay with a separate tree, too. If we go with a separate tree,
we might want to set up something like
[Teamware onnv-clone]
|
|
[Teamware tools clone]--------------[external tools development repo]
to help with merges.
Interesting idea. So take a partial Teamware clone of just the stuff
we're interested in, and bridge that to the Hg repository outside?
Am I understanding that right?
That's reasonable. A little bit more initial legwork - but nothing too bad.
cheers,
steve
--
stephen lau // [EMAIL PROTECTED] | 650.786.0845 | http://whacked.net
opensolaris // solaris kernel development
_______________________________________________
tools-discuss mailing list
tools-discuss@opensolaris.org
