From: Peter Samuelson <peter@cadcamlab.org>
To: Horst von Brand <vonbrand@sleipnir.valparaiso.cl>
Cc: Keith Owens <kaos@ocs.com.au>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] link time error in drivers/mtd (240t13p2)
Date: Mon, 18 Dec 2000 01:47:03 -0600 [thread overview]
Message-ID: <20001218014702.C3199@cadcamlab.org> (raw)
In-Reply-To: <kaos@ocs.com.au> <200012171632.eBHGWGB01116@sleipnir.valparaiso.cl>
In-Reply-To: <200012171632.eBHGWGB01116@sleipnir.valparaiso.cl>; from vonbrand@sleipnir.valparaiso.cl on Sun, Dec 17, 2000 at 01:32:15PM -0300
[Horst von Brand]
> Would tsort(1) perhaps help?
I'm betting Linus would never go for using tsort to resolve such issues
-- unless tsort output is guaranteed to be stable (the docs for GNU
textutils don't say). This would be for the same reason that he
rejected the partial ordering in the LINK_FIRST patch -- because it was
only partial ordering and he thinks total ordering is necessary. For
me, BTW, that's still an article of faith -- I still do not see why
total ordering *is* necessary, but <shrug> thus saith the penguin.
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-18 8:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-16 22:07 [PATCH] link time error in drivers/mtd (240t13p2) Rasmus Andersen
2000-12-16 23:15 ` Keith Owens
2000-12-17 10:01 ` David Woodhouse
2000-12-17 10:32 ` Keith Owens
2000-12-17 10:44 ` David Woodhouse
2000-12-17 10:51 ` Keith Owens
2000-12-17 11:39 ` David Woodhouse
2000-12-17 11:54 ` Keith Owens
2000-12-17 12:04 ` David Woodhouse
2000-12-17 15:20 ` Alan Cox
2000-12-17 16:32 ` Horst von Brand
2000-12-18 7:47 ` Peter Samuelson [this message]
2000-12-17 10:27 ` David Woodhouse
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=20001218014702.C3199@cadcamlab.org \
--to=peter@cadcamlab.org \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=vonbrand@sleipnir.valparaiso.cl \
/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