From: Tom Rini <trini@ti.com>
To: Denys Dmytriyenko <denis@denix.org>
Cc: meta-ti@yoctoproject.org
Subject: Re: release branch for meta-ti?
Date: Mon, 19 Mar 2012 14:05:57 -0700 [thread overview]
Message-ID: <20120319210557.GF19810@bill-the-cat> (raw)
In-Reply-To: <20120319210247.GD15554@denix.org>
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
On Mon, Mar 19, 2012 at 05:02:47PM -0400, Denys Dmytriyenko wrote:
> On Mon, Mar 19, 2012 at 01:58:54PM -0700, Tom Rini wrote:
> > On Mon, Mar 19, 2012 at 01:58:36PM +0100, Koen Kooi wrote:
> > > Hi,
> > >
> > > Any volunteers for maintaining a releasebranch that matches the upcoming oe-core release in ~4 weeks?
> >
> > If Denys or Chase don't step-up, I'll do it. As qualification, I do
> > such a thing for oe-classic currently :) But if either of them would
> > rather, I'll defer to them.
>
> We'll probably need to set meta-oe-maintenance up anyway for meta-arago to
> work with, rather than chasing changes in the master...
Yes, meta-oe will also need a maintenance release to match, and
meta-arago too :)
> BTW, Tom, when are we planning to kill 2011.03 in oe-classic? It's 1 year old
> now...
So long as there's interest has been my statement. Given I was given a
pull request last week, there's still interest :)
--
Tom
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 853 bytes --]
next prev parent reply other threads:[~2012-03-19 21:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 12:58 release branch for meta-ti? Koen Kooi
2012-03-19 20:58 ` Tom Rini
2012-03-19 21:02 ` Denys Dmytriyenko
2012-03-19 21:05 ` Tom Rini [this message]
2012-03-19 21:13 ` Koen Kooi
2012-03-19 21:29 ` Denys Dmytriyenko
2012-03-30 22:09 ` Koen Kooi
2012-03-30 22:17 ` William Mills
2012-03-31 14:27 ` Philip Balister
2012-03-31 15:38 ` Richard Purdie
2012-04-09 2:18 ` Denys Dmytriyenko
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=20120319210557.GF19810@bill-the-cat \
--to=trini@ti.com \
--cc=denis@denix.org \
--cc=meta-ti@yoctoproject.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.