From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: master branch and stabilisation
Date: Thu, 5 Apr 2018 22:01:23 +0300 [thread overview]
Message-ID: <3b467178-c954-4f02-d903-03c8fa9f95a3@linux.intel.com> (raw)
In-Reply-To: <1522947905.11431.438.camel@linuxfoundation.org>
On 04/05/2018 08:05 PM, Richard Purdie wrote:
> So I now get to spend my time trying to figure out which patch broke
> what so I can report back on it and make the branch build again by
> dropping the broken patches.
>
> This means I'm trying to do full on day to day development as usual as
> well as trying to sort release issues like the imminent fedora28 issue
> I should be paying attention to instead.
>
> So, a question, what do people want me to do?
You can file bugs with master-next failures and assign them to me,
without looking at the failed logs at all. Multitasking is stressful for
the brain, much better to do things one after the other than switch
context. And I'm not particularly time crunched now.
We should probably more strictly enforce the freeze - just reject the
patches and ask to rebase and re-send after a specific date.
Alex
next prev parent reply other threads:[~2018-04-05 19:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 17:05 master branch and stabilisation Richard Purdie
2018-04-05 19:01 ` Alexander Kanavin [this message]
2018-04-05 19:03 ` akuster808
2018-04-05 19:43 ` Joshua Watt
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=3b467178-c954-4f02-d903-03c8fa9f95a3@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox