From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] X11 component versions
Date: Mon, 04 Feb 2013 23:06:43 +0100 [thread overview]
Message-ID: <511030F3.1060407@mind.be> (raw)
In-Reply-To: <CAOT3miJUfF3Oc2XFXJRiLCtMxtsHSWZWWLGvGyc+zNkqHGgnEw@mail.gmail.com>
On 04/02/13 22:37, Nicolas Dechesne wrote:
> another question: do we really want to have 100+ patches to upgrade to
> R7.7, or should we make 1 commit that bumps all components (and
> remove/add the relevant ones)? I am asking because i think that any
> 'commit' in between the 100+ patches could put BR in a bad state.. Of
> course if we upgrade just 1 specific component later on (before R7.8
> is made) then it can be made 'manually', but for large release
> upgrade, maybe 1 commit makes sense..
I certainly prefer a single tested patch than 100 patches where the
intermediate steps have not been tested.
The server should perhaps be a separate patch, because it probably
needs changes in the configure options as well. But then again, this
could leave the tree in an unbuildable state...
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:[~2013-02-04 22:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 9:44 [Buildroot] X11 component versions Nicolas Dechesne
2013-02-04 10:45 ` Will Wagner
2013-02-04 10:56 ` Nicolas Dechesne
2013-02-04 11:11 ` Will Wagner
2013-02-04 20:40 ` Thomas Petazzoni
2013-02-04 20:49 ` Nicolas Dechesne
2013-02-04 21:30 ` Thomas Petazzoni
2013-02-04 21:37 ` Nicolas Dechesne
2013-02-04 22:06 ` Arnout Vandecappelle [this message]
2013-02-04 22:41 ` Nicolas Dechesne
2013-02-04 22:24 ` Thomas Petazzoni
2013-02-04 22:45 ` Nicolas Dechesne
2013-02-04 22:54 ` Thomas Petazzoni
2013-02-04 20:42 ` Nicolas Dechesne
2013-02-04 22:46 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2013-03-12 8:52 Jesper Birksø Bækdahl
2013-03-18 8:05 ` Arnout Vandecappelle
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=511030F3.1060407@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