All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@trained-monkey.org>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Ben Greear <greearb@candelatech.com>,
	Petro <petro@auctionwatch.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Eepro100 driver.
Date: Fri, 22 Feb 2002 11:38:14 -0500	[thread overview]
Message-ID: <15478.29686.862941.196746@trained-monkey.org> (raw)
In-Reply-To: <3C767359.44CD415E@mandrakesoft.com>
In-Reply-To: <20020213211639.GB2742@auctionwatch.com> <3C6B2277.CA9A0BF8@mandrakesoft.com> <3C6B406E.1010706@candelatech.com> <3C6B4B20.FE4AE960@mandrakesoft.com> <d3sn7ttrcb.fsf@lxplus050.cern.ch> <3C767359.44CD415E@mandrakesoft.com>

>>>>> "Jeff" == Jeff Garzik <jgarzik@mandrakesoft.com> writes:

Jeff> Jes Sorensen wrote:
>> Would be a lot nicer to see someone spending the time pulling the
>> useful bits out of e100 and putting it into eepro100. e100 is ugly
>> and bloated for no reason.

Jeff> When it passes my review, it will not be.

Jeff> e100 + my desired changes == eepro100 + my desired changes

Guess I just prefer to build bottom up with a basic clean code base
rather than a gross messy and bloated base.

Jes

  reply	other threads:[~2002-02-22 16:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-13 21:16 Eepro100 driver Petro
2002-02-14  2:35 ` Jeff Garzik
2002-02-14  4:43   ` Ben Greear
2002-02-14  5:29     ` Jeff Garzik
2002-02-18  1:52       ` Petro
2002-02-18 21:18         ` Ben Greear
2002-02-22 16:27       ` Jes Sorensen
2002-02-22 16:35         ` Jeff Garzik
2002-02-22 16:38           ` Jes Sorensen [this message]
2002-02-22 20:37           ` endre
2002-02-22 21:57             ` Jeff Garzik

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=15478.29686.862941.196746@trained-monkey.org \
    --to=jes@trained-monkey.org \
    --cc=greearb@candelatech.com \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=petro@auctionwatch.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.