All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Craig <philipc@snapgear.com>
To: Carlos O'Donell <carlos@codesourcery.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: netfilter files in a case-insensitive filesystem
Date: Fri, 02 Jun 2006 10:14:51 +1000	[thread overview]
Message-ID: <447F82FB.7000500@snapgear.com> (raw)
In-Reply-To: <20060601154514.GA4977@lios>

On 06/02/2006 01:45 AM, Carlos O'Donell wrote:
> The current goal is to be able to ship the headers for use in an
> environment which resides on a case-insenstive filesystem.
> 
> If we did the work, would the community accept such patches?

I'm not a core developer, but I'm pretty sure the answer is no.

It's not just the header files.  The source files and modules
also do this, and changing any of these breaks userspace
compatibility.



  reply	other threads:[~2006-06-02  0:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-23 20:27 netfilter files in a case-insensitive filesystem Carlos O'Donell
2006-06-01  5:40 ` Philip Craig
2006-06-01 15:45   ` Carlos O'Donell
2006-06-02  0:14     ` Philip Craig [this message]
2006-06-02 15:24     ` Jozsef Kadlecsik
2006-06-05 13:40       ` Carlos O'Donell

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=447F82FB.7000500@snapgear.com \
    --to=philipc@snapgear.com \
    --cc=carlos@codesourcery.com \
    --cc=netfilter@lists.netfilter.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.