From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH for-2012.11 0/5] Introduce errors for legacy API
Date: Fri, 30 Nov 2012 12:10:57 -0800 [thread overview]
Message-ID: <877gp2am26.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <50AF8F3B.9090504@mind.be> (Arnout Vandecappelle's message of "Fri, 23 Nov 2012 15:59:07 +0100")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
Hi,
Arnout> The problem with warnings is that we produce so much output
Arnout> that they'll just be hidden. They would make sense if an error
Arnout> follows soon after. But in all likelihood, if an error follows,
Arnout> it will be much further down.
Arnout> [snip]
Arnout> So, is there still anything that I should change?
I'm still not 100% happy with it, but I think this is the best we can do
for 2012.11, so I've committed the series, thanks!
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2012-11-30 20:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 20:08 [Buildroot] [PATCH for-2012.11 0/5] Introduce errors for legacy API Arnout Vandecappelle
2012-11-12 20:08 ` [Buildroot] [PATCH for-2012.11 1/5] pkg-infra: introduce " Arnout Vandecappelle
2012-11-12 21:05 ` Thomas Petazzoni
2012-11-12 21:18 ` Arnout Vandecappelle
2012-11-13 8:51 ` Thomas Petazzoni
2012-11-12 20:08 ` [Buildroot] [PATCH for-2012.11 2/5] legacy: move old GENTARGETS macros to Makefile.legacy Arnout Vandecappelle
2012-11-12 20:08 ` [Buildroot] [PATCH for-2012.11 3/5] legacy: add error target for host-pkg-config Arnout Vandecappelle
2012-11-12 20:08 ` [Buildroot] [PATCH for-2012.11 4/5] legacy: evtest is dropped from input-tools package Arnout Vandecappelle
2012-11-12 20:08 ` [Buildroot] [PATCH for-2012.11 5/5] legacy: BR2_PACKAGE_LIBINTL is replaced by gettext Arnout Vandecappelle
2012-11-15 11:23 ` [Buildroot] [PATCH for-2012.11 0/5] Introduce errors for legacy API Peter Korsgaard
2012-11-23 14:59 ` Arnout Vandecappelle
2012-11-30 20:10 ` Peter Korsgaard [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=877gp2am26.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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