From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Branched for release
Date: Thu, 01 Oct 2015 15:24:05 +0100 [thread overview]
Message-ID: <1443709445.14733.5.camel@linuxfoundation.org> (raw)
Just a heads up for people that we've branched for release and that
jethro branches are now available. Bitbake branched as 1.28, I decided
to save bitbake 2.0 for another occasion.
These branches are going to track master for a while yet as we stabilise
the release.
Cheers,
Richard
next reply other threads:[~2015-10-01 14:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 14:24 Richard Purdie [this message]
2015-10-01 14:28 ` Branched for release Khem Raj
2015-10-01 14:41 ` Otavio Salvador
2015-10-01 15:42 ` Richard Purdie
2015-10-01 15:03 ` Carlos Alberto Lopez Perez
2015-10-01 15:23 ` Khem Raj
2015-10-01 15:37 ` Richard Purdie
2015-10-01 17:24 ` Khem Raj
2015-10-01 20:25 ` Richard Purdie
2015-10-01 20:28 ` Khem Raj
2015-10-02 1:37 ` Khem Raj
2015-10-01 20:30 ` Otavio Salvador
2015-10-01 21:16 ` Richard Purdie
2015-10-02 1:46 ` Khem Raj
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=1443709445.14733.5.camel@linuxfoundation.org \
--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