From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: Commits to master in my absence
Date: Mon, 1 Aug 2011 12:25:22 -0700 [thread overview]
Message-ID: <4E36FDA2.7030001@mentor.com> (raw)
In-Reply-To: <1312206333.2344.456.camel@rex>
-----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".
- --
Tom Rini
Mentor Graphics Corporation
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJONv2eAAoJEI4NMjfc3nJxudcIAMg7yMIdl648ZdRsFGAUTKTD
HSP8lLzawtEcl1bxektShH7amCf45wHvlw36joNNt3dG78FwAfO9bozubZEypwcS
N7YXBo8JVJVi1WUIni23CZor4I091Ubt0tEHFOk4iDIyU9B9q+T77xg2qn+r6RJN
7yNzs7XRffM8D2v7OxG/6kK4FvQDflVbnqEYkN+dE0rgUFOMUDdaSkB5JO0NShG2
yYLkXljRNJ24Of5crsuQ/F4Vqk86b41Ax9jYrdFUOl+qgdovbPs3ninKtbDgT9ez
Adh8behhx/LvbQQNldOi0l/UakPAmEPHEjEBNxmKX/GoZjfLHN0nb4Ucy5sAtBM=
=PIo2
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-08-01 19:29 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 [this message]
2011-08-01 19:56 ` Richard Purdie
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=4E36FDA2.7030001@mentor.com \
--to=tom_rini@mentor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox