From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] board-specific autotools env customization
Date: Fri, 06 Feb 2015 11:49:41 +0100 [thread overview]
Message-ID: <54D49C45.40206@mind.be> (raw)
In-Reply-To: <CAKAx1ci_E5=kba_kR8KLt==Q7b_8mKoTeeY=t_XtZ3_x0yh-_g@mail.gmail.com>
On 06/02/15 10:31, Lionel Orry wrote:
[snip]
> Thank you Arnout for your valuable help. I sent a patch to the
> mailing-list, and I am preparing the patch for upstream.
> I have to adapt it for the current upstream master version (v.4.2.x)
> because acinclude.m4 changed, so I can't send it as-is...
> Should I try to send the v4.0.x based patch to their maintenance
> branch ? They say it's for bugfixes only so I'm pretty sure it will be
> rejected.
Sending to the upstream maintenance branch isn't very useful.
Sending an adapted patch to buildroot like you did is OK. But perhaps it's more
useful to bump the buildroot version. Yes, we're trying to squeeze as much
contribution out of you as we can :-)
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2015-02-06 10:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 14:05 [Buildroot] board-specific autotools env customization Lionel Orry
2015-02-02 16:54 ` Thomas Petazzoni
2015-02-02 17:19 ` Lionel Orry
2015-02-03 8:54 ` Arnout Vandecappelle
2015-02-04 7:52 ` Lionel Orry
2015-02-04 20:21 ` Arnout Vandecappelle
2015-02-06 9:31 ` Lionel Orry
2015-02-06 10:49 ` Arnout Vandecappelle [this message]
2015-02-06 14:51 ` Lionel Orry
2015-02-06 14:59 ` Thomas Petazzoni
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=54D49C45.40206@mind.be \
--to=arnout@mind.be \
--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