All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gavin Hemphill <hemphill@drea.dnd.ca>
To: Larry McVoy <lm@bitmover.com>,
	"linuxppc-dev@lists.linuxppc.org"
	<linuxppc-dev@lists.linuxppc.org>
Subject: Re: Problems with linuxppc_2_4_devel
Date: Wed, 16 Jan 2002 11:30:19 -0400	[thread overview]
Message-ID: <3C459C8B.1020203@drea.dnd.ca> (raw)
In-Reply-To: 20020115205755.GF764@cpe-24-221-152-185.az.sprintbbd.net


Couldn't the pre-trigger actually check with an ntp server at the bk end
and put up a warning if the commit times are off by "too much".

Tom Rini wrote:

> On Tue, Jan 15, 2002 at 11:22:33AM -0800, Larry McVoy wrote:
>
>
>>Would you like me to make you a "pre-commit" trigger which catches these
>>problems?
>>
>
> If you've got the time, sure.  Hopefully we're all done breaking our
> clocks tho. :)
>
> --
> Tom Rini (TR1265)
> http://gate.crashing.org/~trini/
>
>
>


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2002-01-16 15:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-15 12:21 Problems with linuxppc_2_4_devel Kenneth Johansson
2002-01-15 16:25 ` Tom Rini
2002-01-15 17:02   ` Gabriel Paubert
2002-01-15 19:22     ` Larry McVoy
2002-01-15 20:57       ` Tom Rini
2002-01-15 21:02         ` Larry McVoy
2002-01-15 21:10           ` Tom Rini
2002-01-16 11:39             ` Gabriel Paubert
2002-01-16 15:07               ` Tom Rini
2002-01-16 18:43                 ` Gabriel Paubert
2002-01-16 11:37           ` Gabriel Paubert
2002-01-17  1:10           ` Paul Mackerras
2002-01-16 11:28         ` Gabriel Paubert
2002-01-16 15:30         ` Gavin Hemphill [this message]
2002-01-16 18:59           ` Gabriel Paubert
2002-01-21  9:21   ` Kenneth Johansson
  -- strict thread matches above, loose matches on Subject: below --
2002-10-10 15:22 Anders Blomdell
2002-10-14 14:37 ` Tom Rini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3C459C8B.1020203@drea.dnd.ca \
    --to=hemphill@drea.dnd.ca \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=lm@bitmover.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.