linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Embedded PPC Linux list <linuxppc-embedded@ozlabs.org>
Subject: Re: [PATCH] first in a series to enhance microcode patches
Date: Tue, 5 Oct 2004 16:00:45 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.60.0410051559560.3683@localhost.localdomain> (raw)
In-Reply-To: <20041005192950.GL32692@smtp.west.cox.net>

On Tue, 5 Oct 2004, Tom Rini wrote:

> On Tue, Oct 05, 2004 at 03:20:37PM -0400, Dan Malek wrote:

>> No, send a whole patch that _does_ something.  Let's see all of these
>> changes at once.  By itself, this patch is useless and doesn't add any
>> features, it just wastes our time discussing it.
>
> A series of inter-dependant patches might be better, but I like small,
> easy to understand patches.

you know, it's a good thing i'm severely bipolar. :-)  somebody needs 
to make a decision -- i'll go with whatever it is.

rday

  reply	other threads:[~2004-10-05 20:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-05 16:32 [PATCH] first in a series to enhance microcode patches Robert P. J. Day
2004-10-05 19:20 ` Dan Malek
2004-10-05 19:29   ` Tom Rini
2004-10-05 20:00     ` Robert P. J. Day [this message]
2004-10-05 20:53       ` Tom Rini
2004-10-05 19:52   ` Robert P. J. Day
2004-10-05 20:20     ` Wolfgang Denk
2004-10-06 13:30       ` Robert P. J. Day
2004-10-06 14:05         ` Mark Chambers
2004-10-06 14:01           ` Robert P. J. Day
  -- strict thread matches above, loose matches on Subject: below --
2004-10-05 17:32 Robert P. J. Day
2004-10-07 15:38 ` 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=Pine.LNX.4.60.0410051559560.3683@localhost.localdomain \
    --to=rpjday@mindspring.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --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).