linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Gabriel Paubert <paubert@iram.es>
Cc: Tom Rini <trini@kernel.crashing.org>,
	Kenneth Johansson <ken@kieraypc01.p.y.ki.era.ericsson.se>,
	"linuxppc-dev@lists.linuxppc.org"
	<linuxppc-dev@lists.linuxppc.org>
Subject: Re: Problems with linuxppc_2_4_devel
Date: Tue, 15 Jan 2002 11:22:33 -0800	[thread overview]
Message-ID: <20020115112233.E15959@work.bitmover.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0201151756200.11139-100000@gra-lx1.iram.es>; from paubert@iram.es on Tue, Jan 15, 2002 at 06:02:30PM +0100


> IOW, check that your clock is not borked before committing changesets...

Would you like me to make you a "pre-commit" trigger which catches these
problems?
--
---
Larry McVoy            	 lm at bitmover.com           http://www.bitmover.com/lm

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

  reply	other threads:[~2002-01-15 19:22 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 [this message]
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
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=20020115112233.E15959@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=ken@kieraypc01.p.y.ki.era.ericsson.se \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=paubert@iram.es \
    --cc=trini@kernel.crashing.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).