Okay, this time the Docs repository is really available.

The bogus "docs" (lower case d) repository is still there
however, so make sure you get the right one.

So far I have made a stab at the ntpd.1m man page, and a
brief encounter with the smf method and manifest. I have
also created empty file for the rest of deliverables.

So, if you want to take a look, go ahead and get them
through anon mercurial access. If you are on the list
of committers then you can get the repository using your
opensolaris ID. If you do not know how to set you ID up
for mercurial on OpenSolaris.org, go to
http://opensolaris.org/os/community/tools/scm/hg_help/

And if you are not on the list of committers but would
like to be, just drop me a line. One caveat, all committers
must be affiliated with the OpenSolaris NTP project.

As near as I can tell, the normal cycle after the
initial clone is:

1. pull
2. update
3. (merge if required)
4. edit
5. commit
6. push

I think that we need to do this in a tight cycle, at least
at first. This is fairly informal collaboration at this point,
so it is more important for us to keep in sync with each other,
rather than worry about strict correctness.

Good luck. Glad to have you on board.

Brian Gupta wrote:
>> hg clone ssh://anon at hg.opensolaris.org/hg/ntp/Docs
> 
> No files?? What did I do wrong?
> 
> bash-3.00# hg clone ssh://anon at hg.opensolaris.org/hg/ntp/Docs
> destination directory: Docs
> no changes found
> 0 files updated, 0 files merged, 0 files removed, 0 files unresolved
> _______________________________________________
> ntp-discuss mailing list
> ntp-discuss at opensolaris.org
> http://opensolaris.org/mailman/listinfo/ntp-discuss

-- 
blu

"When Congress started Daylight Savings Time earlier, did
they even consider what affect an extra hour of daylight
would have on global warming? Well, did they?"
----------------------------------------------------------------------
Brian Utterback - Solaris RPE, Sun Microsystems, Inc.
Ph:877-259-7345, Em:brian.utterback-at-ess-you-enn-dot-kom

Reply via email to