From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Add SUSv3 Legacy Macros config option
Date: Fri, 23 Nov 2007 15:32:38 +0100 [thread overview]
Message-ID: <01d401c82dde$10d9d4c0$dcc4af0a@atmel.com> (raw)
In-Reply-To: 200711231506.58719.atle@nissestad.no
> Sorry if I'm a bit impatient, but could someone with commit-access add the
> patch posted in this issue: http://busybox.net/bugs/view.php?id=1596
> (http://bugs.uclibc.org/file_download.php?file_id=1193&type=bug)
>
> ..or alternatively tell me to use a different approach to fix this issue...
>
The preferred approach is to fix those packages requiring the LEGACY MACROS.
> - Atle
> _______________________________________________
Best Regards
Ulf Samuelsson
next prev parent reply other threads:[~2007-11-23 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-23 14:06 [Buildroot] [PATCH] Add SUSv3 Legacy Macros config option Atle Nissestad
2007-11-23 14:32 ` Ulf Samuelsson [this message]
2007-11-23 15:31 ` Ivan Kuten
2007-11-23 15:05 ` Atle Nissestad
2007-11-23 16:05 ` Bernhard Fischer
2007-11-23 16:03 ` Bernhard Fischer
2007-11-23 16:18 ` Atle Nissestad
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='01d401c82dde$10d9d4c0$dcc4af0a@atmel.com' \
--to=ulf@atmel.com \
--cc=buildroot@busybox.net \
/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