From: Zdenek Kabelac <zdenek.kabelac@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: John Spencer <maillist-lvm@barfooze.de>
Subject: Re: [linux-lvm] [PATCH] fix missing include directives
Date: Thu, 21 Feb 2013 17:54:38 +0100 [thread overview]
Message-ID: <5126514E.8070101@gmail.com> (raw)
In-Reply-To: <5126245F.3050407@barfooze.de>
Dne 21.2.2013 14:42, John Spencer napsal(a):
> On 02/10/2013 12:18 AM, John Spencer wrote:
>> On 02/02/2013 05:14 PM, John Spencer wrote:
>>> on glibc, those are erroneously (namespace pollution) pulled in via
>>> other headers. this doesn't work with conformant libcs (musl libc in
>>> this case), we simply need to include all needed headers.
>>>
>>> Signed-Off-By: John Spencer <maillist-lvm@barfooze.de>
>>>
>>>
>>
>> ping
>
accepted
https://www.redhat.com/archives/lvm-devel/2013-February/msg00033.html
Zdenek
next prev parent reply other threads:[~2013-02-21 16:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-02 16:14 [linux-lvm] [PATCH] fix missing include directives John Spencer
2013-02-09 23:18 ` John Spencer
2013-02-21 13:42 ` John Spencer
2013-02-21 16:54 ` Zdenek Kabelac [this message]
2013-02-21 16:55 ` Zdenek Kabelac
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=5126514E.8070101@gmail.com \
--to=zdenek.kabelac@gmail.com \
--cc=linux-lvm@redhat.com \
--cc=maillist-lvm@barfooze.de \
/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;
as well as URLs for NNTP newsgroup(s).