Richard Lowe writes:
> Bill Sommerfeld <sommerfeld at sun.com> writes:
> > what I think would make sense would be to set a different,
> > non-teamware-specific variable. So a teamware workspace would get
> > CODEMGR_WS and the TBD additional variable; mercurial would just get the
> > TBD additional variable.
>
> I'll leave that for others (Mike?) to comment on, I think. I'm still
> not entirely sold either way.
I've gotten used to this, and it's really not that bad. My precmd
hook looks something like this:
if [ -n "$CODEMGR_WS" -a -d "$CODEMGR_WS/Codemgr_wsdata" ]; then
/usr/ucb/echo -n "ESC""]0;$user$host ws "`basename "$CODEMGR_WS"`"^G"
elif [ -n "$CODEMGR_WS" -a -d "$CODEMGR_WS/.hg" ]; then
/usr/ucb/echo -n "ESC""]0;$user$host hg-ws "`basename "$CODEMGR_WS"`"^G"
else
... and it works whether I'm using new ws or old. I don't think it'd
be any simpler with another variable.
(Though, yeah, I do see the point that $CODEMGR_WS has nothing to do
with Mercurial.)
> >> > usr/src/tools/scripts/nightly.sh
> >> >
> >> > WES-13 I thought bringovercheck was going to be nuked as part of this
> >> > wad.
> >>
> >> That was my original plan, yes. But we will be integrating to onnv
> >> while TeamWare is still in use, both for ON and SFW, bringoverchk has
> >> to stay around until all the gates using it are no longer using
> >> teamware, at least.
> >
> > Last I checked, the bugs that spawned bringovercheck have pretty much
> > all been slain, so it could be retired now even for teamware.
> >
>
> Hm, in that case I think, again, it'd be best if I left that for
> others to respond to.
Yes; it can be nuked. Bill wrote it, so he'd be in the best position
to comment on its usefulness. ;-}
--
James Carlson, Solaris Networking <james.d.carlson at sun.com>
Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
