From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] system: add option to pass extra args to post-build and post-image scripts
Date: Wed, 10 Jul 2013 11:53:52 +0200 [thread overview]
Message-ID: <8738rmhhan.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20130710112939.3cfc5b3b@skate> (Thomas Petazzoni's message of "Wed, 10 Jul 2013 11:29:39 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Thomas> On Wed, 10 Jul 2013 09:16:28 +0200, Thomas Petazzoni wrote:
>> Regarding the patch itself, I'd say why not. I'm just wondering if it
>> wouldn't be better to have separate arguments for both scripts. Not
>> sure.
Thomas> Ok, I see that it has already been committed, without more
Thomas> discussion... Fair enough.
I commented here and on IRC that I didn't really find it nice, but
didn't see any better way of doing it. Your comment seemed to be in line
with that, so I applied.
But I agree, perhaps it would be better to have seperate options for post-build/post-image.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-07-10 9:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 18:06 [Buildroot] [PATCH] system: add option to pass extra args to post-build and post-image scripts Yann E. MORIN
2013-07-09 18:25 ` Baruch Siach
2013-07-09 18:54 ` Yann E. MORIN
2013-07-09 18:35 ` Yann E. MORIN
2013-07-09 21:50 ` Peter Korsgaard
2013-07-10 7:16 ` Thomas Petazzoni
2013-07-10 9:29 ` Thomas Petazzoni
2013-07-10 9:53 ` Peter Korsgaard [this message]
2013-07-10 12:49 ` Thomas Petazzoni
2013-07-10 16:22 ` Yann E. MORIN
2013-07-10 16:17 ` Yann E. MORIN
-- strict thread matches above, loose matches on Subject: below --
2013-07-09 22:00 Yann E. MORIN
2013-07-10 7:31 ` 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=8738rmhhan.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