From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] apply-patches.sh: detect missing patches
Date: Thu, 5 Sep 2013 16:01:35 +0200 [thread overview]
Message-ID: <20130905140135.GC3136@free.fr> (raw)
In-Reply-To: <5228425A.7090502@lucaceresoli.net>
All,
On 2013-09-05 10:35 +0200, Luca Ceresoli spake thusly:
> Thomas Petazzoni wrote:
> >Dear Thomas De Schampheleire,
> >
> >On Thu, 5 Sep 2013 09:03:33 +0200, Thomas De Schampheleire wrote:
> >
> >>>Although I agree with the concept of checking for existence, I'm not
> >>>sure about the action to take.
> >>>Earlier in apply-patches.sh, if a patch is in an unsupported format,
> >>>it is simply skipped (and a message printed). I think the action in
> >>>that case should line up with the nonexisting patch case, so either
> >>>give a warning and continue, or an error and stop.
> >>Any input from others?
> >My general feeling is that when something goes wrong or looks wrong, we
> >should abort with an error, and not try to continue with something
> >more-or-less broken/incorrect.
>
> I agree. Who reads a million lines of build outputwhen make exits returning
> zero? Definitely BR should stop and shout out loud about missing or
> incorrect patches.
I concur: we should abort on incorrect/missing/malformed patch.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2013-09-05 14:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 16:00 [Buildroot] [PATCH] apply-patches.sh: detect missing patches Ralph Siemsen
2013-08-23 10:31 ` Thomas De Schampheleire
2013-09-05 7:03 ` Thomas De Schampheleire
2013-09-05 8:04 ` Thomas Petazzoni
2013-09-05 8:35 ` Luca Ceresoli
2013-09-05 14:01 ` Yann E. MORIN [this message]
2013-09-05 19:20 ` Thomas De Schampheleire
2013-09-11 12:06 ` Ralph Siemsen
2013-09-12 8:08 ` Thomas De Schampheleire
2013-09-13 18:15 ` [Buildroot] [PATCH v2] " Ralph Siemsen
2013-09-13 18:27 ` Yann E. MORIN
2013-09-15 13:37 ` Ralph Siemsen
2013-09-15 14:13 ` [Buildroot] [PATCH v3] " Ralph Siemsen
2013-09-15 20:09 ` Peter Korsgaard
2013-09-16 7:11 ` Peter Korsgaard
2013-09-16 12:46 ` Ralph Siemsen
2013-09-16 20:50 ` Peter Korsgaard
2013-09-16 15:24 ` Thomas Petazzoni
2013-09-16 19:45 ` Ralph Siemsen
2013-09-16 20:07 ` Arnout Vandecappelle
2013-09-16 20:49 ` Peter Korsgaard
2013-09-16 20:51 ` Yann E. MORIN
2013-09-16 20:57 ` Peter Korsgaard
2013-09-16 12:36 ` Ralph Siemsen
2013-09-16 13:42 ` Peter Korsgaard
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=20130905140135.GC3136@free.fr \
--to=yann.morin.1998@free.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.