> Mark> Once the stuff at bottom is linked to manpage/help pages, it looks
> Mark> mostly right.
>
> So I added a working webrev link to the man page section, but someone
> should install the hg man page on muskoka before we enable that link.

The manpage converter is already on onnv:
http://onnv.sfbay/cgi-bin/man?/usr/share/man/man1/hg.1

...or you can use:
http://www.selenic.com/mercurial/hg.1.html

(and then this works for off-SWAN folks)

> I don't know how to link to Mercurial help output.

Sorry, I had in mind:

http://www.selenic.com/mercurial/wiki/index.cgi/Pull
http://www.selenic.com/mercurial/wiki/index.cgi/Merge
http://www.selenic.com/mercurial/hg.1.html#diff

> Mark> The "Sync up your workspace with the clone" could use an example:
>
> Mark>         hg pull -u ssh://onnv.sfbay//export/onnv-clone
>
> Mark> ...and then "Merge if needed," with example:
>
> Mark>         hg merge
>
> Mark> ...and then the "check your diffs" should be followed by "commit"
> Mark> and "recommit if necessary" steps.
>
> Dunno.  I added some examples (per your suggestion), and it doesn't look
> too cluttered.  I did leave recommit to putback.html.

I think that's sensible, and what's there looks good.

> I've updated puttingback.html and the diffs.  I've also added diffs
> to show what I changed since my first attempt at puttingback.html.
>
> A draft putback.html and diffs are also available.

First bullet: it might be time to lose "sparc" vs "sparcv9" 
differentiation.

Missing bullet item: after the "header file" and "EXPORT_SRC" items, do we 
need something about open-only builds?

"All relevant machine architectures" now includes sun4v, dom0, and domU.

We still do adb?  :)

Should "CDE" be something else now?

For the versioning info link, we do NOT want to refer to spec files.  Rod 
will hunt us down and kill us.  We should point this to 
/ws/onnv-gate/usr/src/lib/README.mapfiles.  And the last part of that 
sentence ("...for updating/creating..." can be whacked.

As Rich pointed out, the req.flg should be worded in a way that makes it 
clear that it's still relevant, mainly for xref.  Maybe something like 
"Did you update any appropriate req.flg files, so that 'make cscope' in 
the directories you're changing will pull in the appropriate context for 
these changes?"

--Mark


Reply via email to