From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libtool version update 2.4.2
Date: Mon, 12 Nov 2012 21:57:11 +0100 [thread overview]
Message-ID: <50A162A7.3080901@mind.be> (raw)
In-Reply-To: <20121112112637.42d1a425@skate>
On 11/12/12 11:26, Thomas Petazzoni wrote:
> Stephan,
>
> On Mon, 12 Nov 2012 08:46:26 +0100, Stephan Hoffmann wrote:
>
>> did you ever think about inventing a kind of "testing" branch with a
>> seperate autobuilder running on? That could keep major build problems
>> away from the master branch.
>
> Yes, this has been discussed during the Developers Meeting, at least
> for the "next" branch that gets created once -rc1 is out, to accumulate
> patches for the next release.
Actually it does make sense to have it in general. We could allow more committers
on that branch, and Peter could cherry-pick from it, which could save him a few
seconds per patch. And it could make master slightly more stable, because only
patches that don't kill the autobuilders would get cherry-picked.
Maybe something to discuss in February.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
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
prev parent reply other threads:[~2012-11-12 20:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 12:38 [Buildroot] [PATCH] libtool version update 2.4.2 Alexander Khryukin
2012-11-10 9:53 ` Thomas Petazzoni
2012-11-10 16:31 ` Alexander Khryukin
2012-11-11 22:00 ` Arnout Vandecappelle
2012-11-11 22:05 ` Thomas Petazzoni
2012-11-12 7:46 ` Stephan Hoffmann
2012-11-12 10:18 ` Alexander Khryukin
2012-11-12 10:26 ` Thomas Petazzoni
2012-11-12 20:57 ` Arnout Vandecappelle [this message]
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=50A162A7.3080901@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