On Wed, Nov 29, 2006 at 10:40:52PM -0500, Richard Lowe wrote:
> [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)

And a way of unambiguously determining the parent of a child/local file
and if that parent has deltas not in the child.  This is important to
the way that wx safely collapses deltas in the child file.  Of course
the logic that wx uses to do the collapse is ugly and assumes it's using
SCCS (wx literally replaces the child's SCCS delta file with that of the
parent).  I'm sure this will need updating for a new SCM.

> 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).

-- 
Will Fiveash
Sun Microsystems Inc.
Austin, TX, USA (TZ=CST6CDT)
_______________________________________________
tools-discuss mailing list
tools-discuss@opensolaris.org

Reply via email to