From: Artem Bityutskiy <dedekind1@gmail.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] recv_image: fix __USE_GNU hack
Date: Mon, 27 Sep 2010 09:35:29 +0300 [thread overview]
Message-ID: <1285569329.16181.4.camel@localhost> (raw)
In-Reply-To: <1285537349-6878-1-git-send-email-vapier@gentoo.org>
On Sun, 2010-09-26 at 17:42 -0400, Mike Frysinger wrote:
> The __USE_GNU define is an internal define that source code should never
> be touching. So switch it to the proper exported _BSD_SOURCE define.
>
> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
Pushed, thanks!
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-09-27 6:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-26 18:48 [PATCH] mtd-utils: standardize PROGRAM_NAME Mike Frysinger
2010-09-26 21:41 ` [PATCH] ubi-utils: tweak const strings decls Mike Frysinger
2010-09-27 6:34 ` Artem Bityutskiy
2010-09-26 21:42 ` [PATCH] recv_image: fix __USE_GNU hack Mike Frysinger
2010-09-27 6:35 ` Artem Bityutskiy [this message]
2010-09-27 6:31 ` [PATCH] mtd-utils: standardize PROGRAM_NAME Artem Bityutskiy
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=1285569329.16181.4.camel@localhost \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=vapier@gentoo.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;
as well as URLs for NNTP newsgroup(s).