Derek E. Lewis wrote:
Stephen Lau wrote:
The onnv-gate repository is a live MIRROR of the internal Teamware
onnv-gate workspace. It will be updated as putbacks happen real-time.
Please go to the onnv-notify mailman list(*2) and subscribe if you
would like to receive putback notifications as they happen.
Is it just me or is this definitely not the case? onnv-notify seems to
be out-of-sync with the actual putbacks, as I received a putback
notification yesterday (the 22nd) for "
6418698 PSARC/2005/334 - Packet Filtering Hooks API (fix cstyle)," but
according to the putback log, this was committed on the 21st. I'm also
I see this notification:
http://mail.opensolaris.org/pipermail/onnv-notify/2006-October/002947.html
that went out on Sat Oct 21 @ 23:16:37 PDT
Going into the onnv-gate repository, I see:
changeset: 3001:a0fedf4579de
user: dr146992
date: Sat Oct 21 23:16:22 2006 -0700
summary: 6418698 PSARC/2005/334 - Packet Filtering Hooks API (fix
cstyle)
Is it possible you're getting a mail delay?
getting onnv-notifications (ex. "6367849 kdb5_util will core dump if
krb5.conf doesn't contain default_realm info.") that haven't made it
into onnv-gate, yet.
changeset: 3005:41bbfbd457d9
user: mp153739
date: Mon Oct 23 06:15:58 2006 -0700
summary: 6367849 kdb5_util will core dump if krb5.conf doesn't
contain default_realm info.
There seem to be two issues here. (1) Is onnv-notify really real-time in
regards to putbacks? (whether or not onnv-gate is a mirror of the
internal Teamware repository or not is irrelevant here) (2) Is the
onnv-gate in sync (or really a real-time mirror) of the internal
Teamware repository?
Yes and yes.
When someone internally commits to the internal Teamware onnv-gate
repository, it gets bridged to my internal Hg onnv-gate within a few
seconds. Immediately after the bridge is complete (usually less than 30
seconds, depending on how many SCCS gets the bridge has to execute), it
gets pushed to the external repository. So the external gate shouldn't
lag by more than a minute or so.
Once the external gate receives the `hg push` and completes, it fires
off an email to mailman - so the mailman processing occurs real-time
with regard to the putback completion.
cheers,
steve
--
stephen lau // [EMAIL PROTECTED] | 650.786.0845 | http://whacked.net
opensolaris // solaris kernel development
_______________________________________________
tools-discuss mailing list
tools-discuss@opensolaris.org
