From: Carlos O'Donell <carlos@codesourcery.com>
To: Philip Craig <philipc@snapgear.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: netfilter files in a case-insensitive filesystem
Date: Thu, 1 Jun 2006 11:45:16 -0400 [thread overview]
Message-ID: <20060601154514.GA4977@lios> (raw)
In-Reply-To: <447E7DC9.9010809@snapgear.com>
On Thu, Jun 01, 2006 at 03:40:25PM +1000, Philip Craig wrote:
> On 05/24/2006 06:27 AM, Carlos O'Donell wrote:
> > Such files conflict in a case-insensitive filesystem. This is a problem
> > for users building on Windows, or installing the headers on a Windows
> > case-insensitive filesystems.
> >
> > The structures in the conflicting files seem to have unique names. Is it
> > possible to merge both files together?
>
> Depends what exactly you are trying to do. If you are just trying to
> build an application that uses them, then you could probably merge them;
> have you tried? Building the kernel would require more work.
>
I have not tried merging the headers. I was deffering to the experts to
get an opinion :)
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?
Cheers,
Carlos.
--
Carlos O'Donell
CodeSourcery
carlos@codesourcery.com
(650) 331-3385 x716
next prev parent reply other threads:[~2006-06-01 15:45 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 [this message]
2006-06-02 0:14 ` Philip Craig
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=20060601154514.GA4977@lios \
--to=carlos@codesourcery.com \
--cc=netfilter@lists.netfilter.org \
--cc=philipc@snapgear.com \
/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.