Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] pango: use qemu to generate pango.modules during rootfs construction
Date: Wed, 14 Sep 2011 10:10:04 +0100	[thread overview]
Message-ID: <1315991405.2519.129.camel@phil-desktop> (raw)
In-Reply-To: <CAP9ODKrSgJqnrAmdDiaPtXYGRL-_8JQ7OUZcx92_hJFA-nCjng@mail.gmail.com>

On Tue, 2011-09-13 at 15:33 -0300, Otavio Salvador wrote:
> On Tue, Sep 13, 2011 at 14:25, Phil Blundell <philb@gnu.org> wrote:
> > Do you know how long it's likely to be before this release is complete
> > and the tree is re-opened for development?  I'm a bit unclear what the
> > process is for that.
> 
> Maybe we ought to use a 'next' branch for it?

If master is going to be closed for a long time (weeks/months) then yes,
that seems like a good idea.  If we're only talking about a few days
then it's probably not worth the effort.

p.





  parent reply	other threads:[~2011-09-14  9:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-31 15:35 [PATCH] pango: use qemu to generate pango.modules during rootfs construction Phil Blundell
2011-09-08  1:12 ` Saul Wold
2011-09-09 21:19 ` Saul Wold
2011-09-10  8:24   ` Richard Purdie
2011-09-10  9:28     ` Phil Blundell
2011-09-10  9:54       ` Richard Purdie
2011-09-10 11:53         ` Phil Blundell
2011-09-13 17:08           ` Richard Purdie
2011-09-13 17:14             ` Otavio Salvador
2011-09-13 17:25             ` Phil Blundell
2011-09-13 18:33               ` Otavio Salvador
2011-09-13 18:46                 ` Saul Wold
2011-09-14  9:10                 ` Phil Blundell [this message]
2011-09-11 21:33       ` Phil Blundell

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=1315991405.2519.129.camel@phil-desktop \
    --to=philb@gnu.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