From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] legal info: fix saving of host package licenses
Date: Wed, 13 Nov 2013 10:45:40 +0100 [thread overview]
Message-ID: <20131113104540.1ad534e9@skate> (raw)
In-Reply-To: <CAAXf6LW+_yxwbhZ1M9JdzL+L=wh5koGm7uCk6Q4FkMDkmaArRA@mail.gmail.com>
Dear Thomas De Schampheleire,
On Wed, 13 Nov 2013 10:16:49 +0100, Thomas De Schampheleire wrote:
> > We were already November, 13th, that is 13th days late than the normal
> > -rc1 date, so I definitely support Peter in not having merged all the
> > possible pending features in 2013.11.
> >
> > That's all what time-based releases are for: stopping merging new
> > features at some point, knowing that they will anyway be merged in
> > -next pretty soon and be part of the following release 3 months later.
>
> While I understand and agree with this principle for new patches, I
> think that patches that have just been waiting to be merged are a
> little different, unless there is an expected risk. Version bumps
> clearly add risk, but in my opinion the proposed patches do not.
Well the proposed patches touch the core package infrastructure, which
to me adds more risk than a version bump that may break an isolated
package. I guess it's a matter of perception :)
> Anyway, it's not that big of a deal. Let's focus now on stabilization
> and autobuild fixes.
Agreed :)
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2013-11-13 9:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 22:20 [Buildroot] [git commit] legal info: fix saving of host package licenses Peter Korsgaard
2013-11-13 7:34 ` Thomas De Schampheleire
2013-11-13 7:45 ` Thomas Petazzoni
2013-11-13 8:12 ` Peter Korsgaard
2013-11-13 9:16 ` Thomas De Schampheleire
2013-11-13 9:45 ` Thomas Petazzoni [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=20131113104540.1ad534e9@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