The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Horst von Brand <vonbrand@inf.utfsm.cl>
To: jmerkey@comcast.net
Cc: Horst von Brand <vonbrand@inf.utfsm.cl>,
	linux-kernel@vger.kernel.org, jmerkey@drdos.com
Subject: Re: kallsyms 2.6.8 address ordering
Date: Thu, 19 Aug 2004 21:23:59 -0400	[thread overview]
Message-ID: <200408200124.i7K1Nxe6007696@localhost.localdomain> (raw)
In-Reply-To: Message from jmerkey@comcast.net  of "Thu, 19 Aug 2004 22:43:18 GMT." <081920042243.1790.41252D06000BA3BD000006FE2200762194970A059D0A0306@comcast.net>

jmerkey@comcast.net said:
> Horst von Brand <vonbrand@inf.utfsm.cl> said:
> > This is probably just working to get the most out of the kernel, and the
> > constraint of "making kernel debuggers easy to write" just isn't in the
> > requirements. The kernel hackers (rightly so, IMVHO) reserve the right to
> > change interfases at the drop of a hat. If third parties get burned, just
> > too bad.

> Makes a lot of unnecessary work for others to keep up.

Tough luck.

>                                                         Some of the
> interfaces being changed are broken as a result.

If it isn't an official interface, there is nothing to complain about...

>                                                   It's not progress to
> break something that shouldn't need changing.

Who are you to say they don't need changing?

>                                                Just IMHO....

Just mine.
-- 
Dr. Horst H. von Brand                   User #22616 counter.li.org
Departamento de Informatica                     Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria              +56 32 654239
Casilla 110-V, Valparaiso, Chile                Fax:  +56 32 797513

  reply	other threads:[~2004-08-20 12:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-19 22:43 kallsyms 2.6.8 address ordering jmerkey
2004-08-20  1:23 ` Horst von Brand [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-19 22:40 jmerkey
2004-08-19 23:11 ` Francois Romieu
2004-08-19 19:27 jmerkey
2004-08-19 19:42 ` David S. Miller
2004-08-19 22:07   ` Julien Oster
2004-08-19 19:24 jmerkey
2004-08-19 19:22 jmerkey
2004-08-19 19:14 jmerkey
2004-08-19 18:26 jmerkey
2004-08-19 18:33 ` Christoph Hellwig
2004-08-19 18:10 jmerkey
2004-08-19 18:19 ` Christoph Hellwig
2004-08-19 18:30 ` Rik van Riel
2004-08-19 18:40 ` Richard B. Johnson
2004-08-19 19:00 ` Robin Holt
2004-08-20 11:42   ` Paulo Marques
2004-08-19 20:10 ` Horst von Brand

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=200408200124.i7K1Nxe6007696@localhost.localdomain \
    --to=vonbrand@inf.utfsm.cl \
    --cc=jmerkey@comcast.net \
    --cc=jmerkey@drdos.com \
    --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