From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Commits to master in my absence
Date: Mon, 01 Aug 2011 20:56:47 +0100 [thread overview]
Message-ID: <1312228607.2344.526.camel@rex> (raw)
In-Reply-To: <4E36FDA2.7030001@mentor.com>
On Mon, 2011-08-01 at 12:25 -0700, Tom Rini wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 08/01/2011 06:45 AM, Richard Purdie wrote:
>
> > I'm a little frustrated to see what happened when I was away from a
> > couple of days. I thought we'd agreed we'd queue up patches in a branch
> > and then I'd take care of things when I got back.
>
> So, I agree with everything you did say. But I'd also like to suggest
> we should have gone with "merge everything Monday" not "merge everything
> Wednesday before RP runs off". Yes, this would have meant either moving
> some testing, or having testing also pull from a different (merged)
> branch. And I too was "wait, what, more stuff went in? I thought we
> caught the big problem already".
If I'd merged everything unexpectedly and not communicated the situation
I think that would be bad. As it was, I did merge things but I also
hopefully clearly communicated the issues and the expectation. Master is
the development tip and some instability, particularly as new features
merge is not entirely unexpected at this point in the cycle.
I'd hope we don't end up in a situation like that again, if we do, I'll
see what other options there and weigh them up as the situation
dictates.
Cheers,
Richard
next prev parent reply other threads:[~2011-08-01 20:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 13:45 Commits to master in my absence Richard Purdie
2011-08-01 17:59 ` Khem Raj
2011-08-01 19:25 ` Tom Rini
2011-08-01 19:56 ` Richard Purdie [this message]
2011-08-01 20:18 ` Tom Rini
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=1312228607.2344.526.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox