From: Adrian Bunk <bunk@stusta.de>
To: akuster808 <akuster808@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [oe-commits] [openembedded-core] branch thud updated (ad0a553 -> 748f946)
Date: Sun, 17 Mar 2019 15:08:36 +0200 [thread overview]
Message-ID: <20190317130836.GA3809@localhost> (raw)
In-Reply-To: <ed62bdd5-c9ad-1796-2330-960d6072317d@gmail.com>
On Sat, Mar 16, 2019 at 08:50:13AM -0700, akuster808 wrote:
> On 3/16/19 5:20 AM, Andreas Müller wrote:
>...
> > 2. This was applied on Feb 6th which is not 3 month back exactly.
> then its worst than I thought, I can't remember what my thought process
> was back to Feb 6th.
> >
> > [1] https://wiki.yoctoproject.org/wiki/Stable_branch_maintenance#Point_release
>
> I am glad you are bringing these things up, it helps me revisit my own
> processes and help me improve.
>
> We are planning on revising the maintenance guidelines soon so I hope to
> get your input.
Was the boost upgrade in thud sent to the mailing list for review?
My reading of the "Requesting a fix in a stable branch" section
would be that this is already a mandatory part of the process.
> - armin
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-03-17 13:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <154947113576.452.14618413373824638023@git.openembedded.org>
2019-03-15 17:16 ` [oe-commits] [openembedded-core] branch thud updated (ad0a553 -> 748f946) Andreas Müller
2019-03-15 17:24 ` Andreas Müller
2019-03-16 11:11 ` akuster808
2019-03-16 12:20 ` Andreas Müller
2019-03-16 15:50 ` akuster808
2019-03-17 13:08 ` Adrian Bunk [this message]
2019-03-17 15:38 ` akuster808
2019-03-17 16:25 ` Adrian Bunk
2019-03-17 16:40 ` akuster808
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=20190317130836.GA3809@localhost \
--to=bunk@stusta.de \
--cc=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.