From: Tim Deegan <tim@xen.org>
To: Christoph Egger <Christoph.Egger@amd.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: RFC PATCH: bring OpenBSD stdarg in line with FreeBSD one
Date: Fri, 27 Jan 2012 10:26:35 +0000 [thread overview]
Message-ID: <20120127102635.GA11163@ocelot.phlegethon.org> (raw)
In-Reply-To: <4F2277C9.10207@amd.com>
At 11:09 +0100 on 27 Jan (1327662553), Christoph Egger wrote:
> On 01/26/12 16:45, Tim Deegan wrote:
> >At 16:16 +0000 on 19 Jan (1326989786), Tim Deegan wrote:
> >>Having an absolute path in a #include confuses distcc's pump mode.
> >>Since AFAICS OpenBSD's stdarg handling uses the builtins, I think we
> >>should just treat it like we do NetBSD.
> >>
> >>I don't have an OpenBSD box to test on, though. :( Any OpenBSD
> >>enthusiasts care to comment?
> >
> >No complaints, and the new header compiles on OpenBSD, so I've applied it.
>
> ... the commit message does not match what the actually patch does.
> You mixed up FreeBSD with NetBSD. :-)
Augh, so I have!
Tim.
prev parent reply other threads:[~2012-01-27 10:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 16:16 RFC PATCH: bring OpenBSD stdarg in line with FreeBSD one Tim Deegan
2012-01-26 15:45 ` Tim Deegan
2012-01-27 10:09 ` Christoph Egger
2012-01-27 10:26 ` Tim Deegan [this message]
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=20120127102635.GA11163@ocelot.phlegethon.org \
--to=tim@xen.org \
--cc=Christoph.Egger@amd.com \
--cc=xen-devel@lists.xensource.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 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).