public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: esr@thyrsus.com
Cc: Horst von Brand <brand@jupiter.cs.uni-dortmund.de>,
	linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: Re: CML2-2.1.3 is available
Date: Thu, 17 Jan 2002 08:53:59 +0000	[thread overview]
Message-ID: <3515.1011257639@redhat.com> (raw)
In-Reply-To: <20020116204345.A22055@thyrsus.com>
In-Reply-To: <20020116204345.A22055@thyrsus.com>  <20020116164758.F12306@thyrsus.com> <esr@thyrsus.com> <200201162156.g0GLukCj017833@tigger.cs.uni-dortmund.de> <20020116164758.F12306@thyrsus.com> <26592.1011230762@redhat.com>


esr@thyrsus.com said:
>  Wha's happened is that I, and others, have merged in a lot of
> information  about what cards can be plugged into which platforms.
> That information has been turned into dependency/visibility rules. 

> Here are some examples from the network cards... 

Hmmm, yes. I think I see at least two errors in that small selection, if I
understand it correctly. But as these are obviously behavioural changes, and
you've said you won't make behavioural changes in the first push of CML2 to
Linus, we can safely ignore them for now - they're lined up for your second
wave of patches, right?

This is why the behavioural changes must be separate from the initial
conversion, btw. They _do_ need separate attention from the gruntwork of
translating CML1 to CML2.

--
dwmw2



  parent reply	other threads:[~2002-01-17  8:54 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-15 19:53 CML2-2.1.3 is available Eric S. Raymond
2002-01-15 20:15 ` Nicolas Pitre
2002-01-15 20:18   ` Eric S. Raymond
2002-01-15 20:41     ` Nicolas Pitre
2002-01-15 19:19       ` Rob Landley
2002-01-16  3:48         ` Eric S. Raymond
2002-01-16  6:29           ` Peter Samuelson
2002-01-16  6:32             ` Eric S. Raymond
2002-01-16  7:13               ` Peter Samuelson
2002-01-16  6:36             ` Alexander Viro
2002-01-16  0:15     ` Henning P. Schmiedehausen
2002-01-15 20:16 ` Anton Altaparmakov
2002-01-15 20:24   ` Eric S. Raymond
2002-01-15 19:30     ` Rob Landley
2002-01-16  3:58       ` Eric S. Raymond
2002-01-15 20:25 ` Russell King
2002-01-15 19:37   ` Rob Landley
2002-01-17  1:18     ` Val Henson
2002-01-21 16:22     ` Daniel Phillips
2002-01-21 17:05       ` [kbuild-devel] " Giacomo Catenazzi
2002-01-21 23:11         ` Daniel Phillips
2002-01-22  6:29           ` Kai Henningsen
2002-01-23 21:45         ` Daniel Phillips
2002-01-16  0:38   ` Peter Samuelson
2002-01-15 20:26 ` Ross Vandegrift
2002-01-16  4:02   ` Eric S. Raymond
2002-01-16 16:38     ` Ross Vandegrift
2002-01-16 16:59       ` Ross Vandegrift
2002-01-16 18:29       ` Rob Landley
2002-01-18 18:32     ` Ross Vandegrift
2002-01-22  5:31       ` Eric S. Raymond
2002-01-15 20:27 ` Robert Love
2002-01-15 21:09 ` David Lang
2002-01-16 15:06 ` Horst von Brand
2002-01-16 21:31   ` Eric S. Raymond
2002-01-16 21:56     ` Horst von Brand
2002-01-16 21:47       ` Eric S. Raymond
2002-01-17  1:26       ` David Woodhouse
2002-01-17  1:43         ` Eric S. Raymond
2002-01-17  8:53         ` David Woodhouse [this message]
2002-01-17 13:37           ` Eric S. Raymond
2002-01-17 14:09           ` David Woodhouse
2002-01-17 14:29             ` Eric S. Raymond
2002-01-16 23:36     ` David Lang
2002-01-18  6:48       ` Kai Henningsen
  -- strict thread matches above, loose matches on Subject: below --
2002-01-22  9:11 [kbuild-devel] " Giacomo Catenazzi
2002-01-22  9:20 ` Keith Owens
     [not found] <fa.d4sn1fv.b78io8@ifi.uio.no>
     [not found] ` <fa.i3p6mlv.1mg2frl@ifi.uio.no>
2002-01-22 10:09   ` Giacomo Catenazzi
2002-01-22 10:25     ` Keith Owens
2002-01-22 10:48       ` Giacomo Catenazzi
2002-01-22 10:53         ` Keith Owens

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=3515.1011257639@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=brand@jupiter.cs.uni-dortmund.de \
    --cc=esr@thyrsus.com \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.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