From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] config: bump linux kernel to 4.8.6 in synopsys defconfigs
Date: Mon, 14 Nov 2016 18:15:16 +0100 [thread overview]
Message-ID: <20161114171516.GB3399@free.fr> (raw)
In-Reply-To: <1479134749.4408.54.camel@synopsys.com>
Alexey, All,
On 2016-11-14 14:46 +0000, Alexey Brodkin spake thusly:
[--SNIP--]
> The point is we were sitting on the patch for quite some time and when we saw
> RC1 was cut (as always unexpectedly :)) simply sent out what we had in our tree.
"Unexpectedly" is a bit of untrue: we've been doing releases every three
months since February 2009, 7 years ago, with a one-month freeze before
the release.
So, anything that comes on-or-after the first day of the release month is
not guaranteed to go in master, unless it is a fix.
This is far from "unexpected". ;-)
Granted, the rc1 tag can be (and has often been) delayed by a few days,
but this is a minor delay; it has never been guaranteed the first few
days of the stabilisation month would still be open for merging into
master...
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2016-11-14 17:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 15:53 [Buildroot] [PATCH] config: bump linux kernel to 4.8.6 in synopsys defconfigs Vlad Zakharov
2016-11-11 14:18 ` Thomas Petazzoni
2016-11-14 12:32 ` Vlad Zakharov
2016-11-14 14:07 ` Thomas Petazzoni
2016-11-14 14:34 ` Alexey Brodkin
2016-11-14 14:42 ` Thomas Petazzoni
2016-11-14 14:46 ` Alexey Brodkin
2016-11-14 15:14 ` Thomas Petazzoni
2016-11-14 17:15 ` Yann E. MORIN [this message]
2016-11-14 17:26 ` Alexey Brodkin
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=20161114171516.GB3399@free.fr \
--to=yann.morin.1998@free.fr \
--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