From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Updated package download address. Added staging option so that applications that depend on rtai's headers may be built by buildroot. Re-directed the include dir to /usr/include/rtai.
Date: Thu, 20 Feb 2014 21:08:57 +0100 [thread overview]
Message-ID: <20140220210857.3907b772@skate> (raw)
In-Reply-To: <1795639.hLW96TZBfD@eclipse>
Dear Andrew Barnes,
On Thu, 20 Feb 2014 16:49:03 +0000, Andrew Barnes wrote:
> Technically no. I did it all with 4.0, but we agreed that changing the version
> number should be a separate patch. Although I don't think there would be a
> problem applying the same changes to 3.9 (I am very sure the project
> infrastructure is identical) I do see the need to test this first. I'm not
> quite in a position to test it at the moment.
>
> what are the next steps, do I resubmit with changes in exactly the same way?
> i initially submitted?
I'd say you can probably include the bump to 4.0 in the same patch.
Normally we prefer patches that do one thing and only one thing, but in
this case, the changes are relatively small, so maybe just one patch
is good enough.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-02-20 20:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 16:26 [Buildroot] [PATCH 1/1] Updated package download address. Added staging option so that applications that depend on rtai's headers may be built by buildroot. Re-directed the include dir to /usr/include/rtai Andrew Barnes
2014-02-20 16:37 ` Thomas Petazzoni
2014-02-20 16:49 ` Andrew Barnes
2014-02-20 20:08 ` Thomas Petazzoni [this message]
2014-04-12 21:11 ` 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=20140220210857.3907b772@skate \
--to=thomas.petazzoni@free-electrons.com \
--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