From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Date: Tue, 18 Feb 2014 11:21:28 -0700 Subject: [U-Boot] Pull request: u-boot-arm/master In-Reply-To: <20140218175040.GH19081@bill-the-cat> References: <20140213184341.3364b092@lilith> <20140218175040.GH19081@bill-the-cat> Message-ID: <5303A4A8.6070104@wwwdotorg.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 02/18/2014 10:50 AM, Tom Rini wrote: > On Thu, Feb 13, 2014 at 06:43:41PM +0100, Albert ARIBAUD wrote: > >> Hi Tom, >> >> The following changes since commit >> 0876703cf2ee107372b56037d4eeeb7604c56796: >> >> boards.cfg: Keep the entries sorted (2014-01-27 08:28:35 -0500) >> >> are available in the git repository at: >> >> git://git.denx.de/u-boot-arm master >> >> for you to fetch changes up to 9c134e189a95c976dab94d4f28444a5398627188: >> >> arm/km: introduce kmsugp1 target (2014-02-13 17:45:36 +0100) ... > Applied to u-boot/master, thanks! How often does u-boot/master get pushed, and is there any replication delay once it does? The most recent commit I see in u-boot/master was committed on Feb 7. Since these emails are a trigger for me and others to go grab the latest commits, it'd be nice if there was at most a very tiny delay between receiving the email, and actually being able to pull the commits. Last time I had this issue, I think I had to wait over 24 hours for the push or replication delay, which was a bit annoying, since I needed to remember to go back and check every so often. If it's replication delay, perhaps the Linux Foundation's kernel.org code could be stolen; that does (almost?) real-time replication from the push-to servers to the public r/o-mirrors, triggered by the git push action. That makes my life a lot easier, since I can "git push" then immediately send the "applied" email.