public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian May <bam@snoopy.apana.org.au>
To: Brian Wellington <bwelling@xbill.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fix for include/linux/fs.h in 2.4.0 kernels
Date: 03 Feb 2001 15:41:43 +1100	[thread overview]
Message-ID: <844rycjs3c.fsf@snoopy.apana.org.au> (raw)
In-Reply-To: <Pine.LNX.4.21.0102022039210.12394-100000@anomaly.xbill.org>
In-Reply-To: Brian Wellington's message of "Fri, 2 Feb 2001 20:39:41 -0800 (PST)"

>>>>> "Brian" == Brian Wellington <bwelling@xbill.org> writes:

    Brian> No, it clearly says that glibc contains its own versions of
    Brian> the net/* and scsi/* files, and that /usr/include/asm and
    Brian> /usr/include/linux should remain as they were.  Since they
    Brian> were symlinks in libc5 (which is what 'originally' seems to
    Brian> be referring to), they should still be symlinks.

Oh I see now.

Sorry for any confusion caused.
-- 
Brian May <bam@snoopy.apana.org.au>
-
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/

  reply	other threads:[~2001-02-03  4:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-03  2:49 Fix for include/linux/fs.h in 2.4.0 kernels Frédéric L. W. Meunier
2001-02-03  3:03 ` Brian May
2001-02-03  3:10 ` Keith Owens
2001-02-03  4:21   ` Brian May
2001-02-03  4:39     ` Brian Wellington
2001-02-03  4:41       ` Brian May [this message]
2001-02-03  8:48   ` Graham Murray
2001-02-03  8:59     ` Keith Owens
2001-02-03 10:09       ` Graham Murray
2001-02-03 11:38         ` Keith Owens
  -- strict thread matches above, loose matches on Subject: below --
2001-02-02 23:04 Jocelyn Mayer
2001-02-02 23:25 ` Keith Owens
2001-02-03  7:42   ` Alan Cox

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=844rycjs3c.fsf@snoopy.apana.org.au \
    --to=bam@snoopy.apana.org.au \
    --cc=bwelling@xbill.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox