Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Heads Up: Bitbake minimum version change imminent
Date: Tue, 05 Jul 2011 15:42:05 +0100	[thread overview]
Message-ID: <1309876925.20015.718.camel@rex> (raw)
In-Reply-To: <BANLkTiktykyb-X0v2W7Hd926ikOkkja8Pw@mail.gmail.com>

On Tue, 2011-06-28 at 09:26 -0700, Chris Larson wrote:
> On Tue, Jun 28, 2011 at 7:31 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > I just wanted to let people know that we have a minimum version of
> > bitbake change imminent for OE-Core.
> >
> > I've already pushed the changes we need to bitbake for umask, shared
> > work directory and multilib and updated its version to 1.13.2. I'm
> > planning to merge patches to OE-Core which depend on these changes later
> > this week (and bump the minimum version OE-Core requires at the same
> > time).
> >
> > In case it isn't clear, I've been batching things up to try and ensure
> > we only have to do this once for a variety of improvements :)
> 
> I have to say that it's *extremely* unintuitive to have a minimum
> version requirement on a version that hasn't even been tagged in the
> git repository. If it's good enough to depend on, it should be good
> enough to consider released.

Agreed and I did add the tags.

Cheers,

Richard




      reply	other threads:[~2011-07-05 14:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-28 14:31 Heads Up: Bitbake minimum version change imminent Richard Purdie
2011-06-28 16:26 ` Chris Larson
2011-07-05 14:42   ` Richard Purdie [this message]

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=1309876925.20015.718.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