> Hello,
>
> Would you kindly take a look at the "General Mercurial" doc and let me know 
> your thoughts.  We think it's near completion and would like any feedback 
> from the team.
>
> http://www.opensolaris.org/os/community/tools/scm/hg_help/
>
> Thanks,
> Linda

mjn-01  "How to install Mercurial" section: we're so far along that this
        whole section should just say "We require at least version 1.0 of
        Mercurial, which was integrated in build 89.  You should install
        SXDE or SXCE builds 89 or later, or install OpenSolaris 2008.05
        and do an image-update."

mjn-02  I didn't take the time to search for it, but aren't there
        instructions elsewhere on os.o about how to setup an ssh key?  If
        not, there should be.  This stuff shouldn't be buried in hg_help,
        since it's also necessary for voting.

mjn-03  In the "How to get started with Mercurial" section, the first
        paragraph (about the Mercurial website) should include a
        recommendation to read the book, which is described on the
        Mercurial website as "the unofficial manual."

mjn-04  I don't think we want to point people to Martin Englund's blog any
        more.  We need a current, accurate, cdm-aware version of this
        information.

mjn-05  This page needs an explanation of the Mercurial working directory.

mjn-06  This page needs to describe the merge process.

mjn-07  This page needs to describe the permitted branch structures, and
        use of recommit to manage changesets on a developer branch.

mjn-08  This page needs to describe the conditions under which you would
        choose to use the mq extension, and then link to a separate page
        with more information on mq.

mjn-09  This page needs to tell a user how to get on the notification list
        for a repository (the equivalent of editing the old Teamware
        Codemgr_wsdata/notification file.)

mjn-10  The hg outgoing example should include the "-v" option.

mjn-11  meta-comment: some of these will probably be satisfied by simply
        getting a better "old way to new way" cheat sheet.

Reply via email to