>>>>> "Mark" == Mark J Nelson <Mark.J.Nelson at Sun.COM> writes:

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

Mark> (and then this works for off-SWAN folks)

True, but there could be confusion in the future, if the web page on
selenic.com refers to a version that is different from what's bundled in
(Open)Solaris.

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

This has the same possible consistency issue as above.  But if you think
the benefits of having hyperlinks here outweigh the confusion risk, I
could certainly put in these links (and use selenic.com for the hg man
page link).  Let me know what you want to do.

>> A draft putback.html and diffs are also available.

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

Sure; removed.

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

Good idea.  I've added a bullet about that.

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

I've added those.  Is it worth distinguishing "sun4v" from "MP sun4v"?

Mark> We still do adb?  :)

I took out the adb reference.

Mark> Should "CDE" be something else now?

Changed to "GNOME/JDS".

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

Okay, I've made the changes that you requested, but please review that
bullet to see if more work is needed.  Is 2002/300 still the right PSARC
case to point people at?

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

I reworded that item; please review.

Rich also suggested a reminder to review diffs, so I added that (before
the one for pbchk).

I've posted a new version of putback.html and putback.diffs.txt, and
I've added diffs since the previous version (for putback.html).

mike

Reply via email to