Re: linux-next: manual merge of the net tree with the net-current tree

From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
Date: Mon, 23 Nov 2009 13:04:41 +1100

Did you push them out? master was down for a while yesterday ...

That's what happened, I couldn't push out yesterday because
master wasn't responding. Let me push it out right now :-)

Thanks!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: What DBMS jobs and database links required for Materialized view replication?
    ... do I need a push job from the master to the snapshot site? ... -who owns the database link on the master site? ...
    (comp.databases.oracle.server)
  • FW: NIM push latency
    ... on the master shows that the Cstate doesn't change from "ready for NIM ... wait (roughly 5 minutes before any events occur on the client). ... any NIM actions that I push from my master. ...
    (AIX-L)
  • NIM push latency
    ... any NIM actions that I push from my master. ... Can anyone point me to what may be causing this delay before execution? ...
    (AIX-L)
  • Re: Moving kerberos infrastructure
    ... kadmind on the master, dump a new database with kdb5_util, and push it to ... the new master with kprop. ... and start the KDC and kadmind on the new master. ... periodic kprop job on the new master to push to the slaves (and make sure ...
    (comp.protocols.kerberos)
  • Re: Moving kerberos infrastructure
    ... Also remember to manually push the ovsec dump across to the new master ... and pull it in (this cannot be done via kprop IIRC). ... Another useful way to think of this is to add the new master as a slave ...
    (comp.protocols.kerberos)