From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] BR2_EXTERNAL: check it is a valid BR2_EXTERNAL dir before using it
Date: Wed, 22 Jan 2014 22:10:50 +0100 [thread overview]
Message-ID: <20140122211050.GC3592@free.fr> (raw)
In-Reply-To: <1880877953.4607498.1390394593186.JavaMail.root@openwide.fr>
J?r?my, All,
On 2014-01-22 13:43 +0100, Jeremy Rosen spake thusly:
> my remark about the error message still not being clean still stands
>
> and the doc is not explicit about Config.in and external.mk being
> required
Hopefully, my new series will address those two points.
> if you don't want to add these to your patch I can post a separate
> one, but for the technical part :
>
> Tested-by: J?r?my Rosen <jeremy.rosen@openwide.fr>
Thank you!
I haven't included your Tested-by in the new series, though, since I've
modified it more than a bit. Care to have a quick look?
Thanks for the feedback! :-)
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:[~2014-01-22 21:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 21:04 [Buildroot] [PATCH] BR2_EXTERNAL: check it is a valid BR2_EXTERNAL dir before using it Yann E. MORIN
2014-01-22 9:00 ` Jeremy Rosen
2014-01-22 10:21 ` yann.morin.1998 at free.fr
2014-01-22 12:43 ` Jeremy Rosen
2014-01-22 21:10 ` Yann E. MORIN [this message]
2014-01-22 18:55 ` Yann E. MORIN
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=20140122211050.GC3592@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox