All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@mandrakesoft.com>
To: Keith Owens <kaos@melbourne.sgi.com>
Cc: Christoph Hellwig <hch@caldera.de>,
	kdb@oss.sgi.com, linux-kernel@vger.kernel.org,
	linux-ia64@linuxia64.org
Subject: Re: Announce: kdb v1.9 is available for kernel 2.4.16
Date: 03 Dec 2001 15:38:50 +0100	[thread overview]
Message-ID: <m2g06s5pxh.fsf@trasno.mitica> (raw)
In-Reply-To: <5112.1007368812@ocs3.intra.ocs.com.au>
In-Reply-To: <5112.1007368812@ocs3.intra.ocs.com.au>

>>>>> "keith" == Keith Owens <kaos@melbourne.sgi.com> writes:

keith> On Mon, 3 Dec 2001 08:43:10 +0100, 
keith> Christoph Hellwig <hch@caldera.de> wrote:
>> On Mon, Dec 03, 2001 at 05:11:31PM +1100, Keith Owens wrote:
>>> This will probably be the last release of kdb using this patch format.
>>> I plan to split kdb into a core patch and smaller arch dependent
>>> patches, instead of one big patch for each arch.
>> 
>> Why can't you release one kdb patch instead?

keith> Because every architecture except i386 differes from the base kernel.
keith> IA64 has its own large patch set that has to be applied to the main
keith> kernel before kdb can be applied.  Sparc uses the vger kernel tree.
keith> The -ac trees are different again.

That is bad, now that you are able to create a kernel that will
compile in i386 & ia64 with latest ia64 patch, I will also like to
be able to integrate kdb there with support for both archs.

Later, Juan.


-- 
In theory, practice and theory are the same, but in practice they 
are different -- Larry McVoy

  reply	other threads:[~2001-12-04  2:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-03  6:11 Announce: kdb v1.9 is available for kernel 2.4.16 Keith Owens
2001-12-03  7:43 ` Christoph Hellwig
2001-12-03  8:40   ` Keith Owens
2001-12-03 14:38     ` Juan Quintela [this message]
2001-12-04  1:50 ` [Linux-ia64] " Hiro Yoshioka
2001-12-04  2:28   ` Keith Owens
2001-12-04 11:36     ` David Woodhouse
2001-12-04 18:04       ` slurn

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=m2g06s5pxh.fsf@trasno.mitica \
    --to=quintela@mandrakesoft.com \
    --cc=hch@caldera.de \
    --cc=kaos@melbourne.sgi.com \
    --cc=kdb@oss.sgi.com \
    --cc=linux-ia64@linuxia64.org \
    --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 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.