[EMAIL PROTECTED] writes:
> Thanks James (and Richard). I run webrev and get:
>
> bash-3.2$ webrev
> Unable to determine SCM type currently in use.
> For teamware: webrev looks for $CODEMGR_WS either in
> the environment or in the file list.
> bash-3.2$
You should generally use "ws" to enter a workspace, like this:
ws /lenovahd/max/onnv-gate
(Assuming that's the name of your project gate.)
> Then I try using a file list:
>
> bash-3.2$ cat file.list
> CODEMGR_WS=/lenovahd/max/onnv-gate
> usr/src/cmd/zdb/zdb.c
You shouldn't need to do that. hg will automatically keep track of
the files you've modified, and webrev will use that list.
> bash-3.2$ webrev file.list
> SCM detected: teamware
> File list from: file.list
> /opt/onbld/bin/webrev[1712]: workspace: not found
> : no such parent workspace
> bash-3.2$
It thinks you're trying to use Teamware because you gave it an
explicit file list and a Teamware path ... and did so from outside of
Sun. That's not likely to work.
> I guess I don't have a workspace. /lenovahd/max/onnv-gate is downloaded
> from mercurial. Is there
> something else I am supposed to do to set up a workspace? I went
> through this before back in
> September, and got it to work eventually (with help from people here).
As long as that's really a Mercurial workspace, all you should need is
the _current_ set of tools. Visit the SCM Migration page to download
the latest package (under "Downloads"):
http://www.opensolaris.org/os/project/scm-migration/
then pkgrm the old stuff (where'd you get it?) and pgkadd the current
one.
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
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
_______________________________________________
tools-discuss mailing list
[email protected]
