James Carlson <[EMAIL PROTECTED]> writes: > [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.)
ws from either onnv-gate or onnv-scm won't work entirely correctly for people off SWAN (it doesn't read env files obviously, and it doesn't attempt to guess what it should do). >> 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. Right, it will, but he was using the onnv-gate webrev, or we'd have guessed Hg in the output above. (of course, if this does turn out to be the webrev from onnv-scm, we need bug reports if it's missing the SCM type) -- Rich _______________________________________________ tools-discuss mailing list tools-discuss@opensolaris.org
