Stephen Hahn wrote:
* Stephen Lau <[EMAIL PROTECTED]> [2006-11-29 16:39]:
Okay, so we have the list of tools we need to port at:
http://opensolaris.org/sc/src/scm-migration/docs/devtools.html
(it's updated from the SCM repository)
There are a few more issues to discuss (from the design document):
use of forest and use of mq. wx-equivalent operations for a developer
are pretty dependent on the latter; handling of bringover-equivalent
operations in nightly depend on the former (for contributors with
access to usr/closed and other potentially separated subtrees).
So now comes the fun part, who wants to work on what?
IIRC, Darren Moffat volunteered to do webrev. I know Rich Lowe has done
*some* work on wx, whether that translates into him volunteering for
it... well, we'll see. I'll just publicly call him out here and see
what his response is ;-)
It's a bit more complicated than that, of course. (But nothing Rich
couldn't handle. :) ) There is functionality in wx that we would like
to make accessible from the hooks, as well as available to the
developer. (In fact, one idea--Danek's, but I think it's very
appealing--is to have the commit hook on the developer side and one or
more of the accept hooks on the server side run the same checks, or at
least share a common subset.) This would necessitate some
reimplementation in Python, I expect.
[This mail in no way constitutes volunteering :)]
Reimplementation outside of wx, certainly. I'm not sure reimplementing
those commands that are currently standalone is a good idea (aren't
some of them used by consolidations not moving to hg?)
Do we have an idea which consolidations currently use wx, and what SCM
they're heading toward (if they're moving)?
Most of what wx needs from the SCM comes down to:
o Workspace, Parent workspace (workspace name, workspace parent)
o Which files changed (active list, putback -n)
o What were the comments associated with those changes (active list,
putback -n, sccs prt)
Much of the rest (checks, review, backup) are SCM agnostic, or at the
very least SCM apathetic, and it'd be nice to see them work wherever
they're needed.
The ability to get at the parent's version of files would obviously be
useful for webrev, and hooked checks too (the hooks currently only mail
on checks if a putback introduces new problems).
-- Rich
_______________________________________________
tools-discuss mailing list
tools-discuss@opensolaris.org
