From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe] matching release branch for upcoming oe-core release
Date: Fri, 30 Mar 2012 11:38:07 -0700 [thread overview]
Message-ID: <jl4ui1$5d2$1@dough.gmane.org> (raw)
In-Reply-To: <jk7ah9$ct6$1@dough.gmane.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 19-03-12 05:58, Koen Kooi schreef:
> Hi,
>
> Any volunteers for maintaining a releasebranch that matches the upcoming
> oe-core release in ~4 weeks?
No one?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org
iQIcBAEBAgAGBQJPdf2NAAoJEHZqAkdh1vT6Z7kP/3PiBj9D26CQFV4dREvYnRmz
+QPLA8LJ70tyJdgqAuAS65hzXq0nV4ZIqrp65js6DXtfEtHPb92ZWFTfAlCtHnSu
OMViJ3Hn2JCSPxDsBfkx4akiEjLGKSCBki1IHV9mJZ7CYgLFSx6n9rSLA1HPRyjD
hfW114gF+o7l8LSzlIktmZnBUcw6kzQ2AY5z9TukohNvJ19EhvaRRKb83V4W7XNX
xAjkqFsYpV1MdLAMsauY4eXNgXuYcT12UksUzCr6nrYL4v5ZpnUmwVSnNOy1fwp7
9oLMVEcNpAGpNrsP0VA+5g3q4PpphToN/uJ2mck/EZRXN0nOU1BA5kCFUNIs5HP4
4An277J1Mdbith45JSx1adgNUNzAlcZ1Bd796GzQhPBHQb8o3dp+PpQLO6rFAfrq
2kqHE9ut6n+dY9Y/VDSLyFCbly5e9Drsl4COkx9HajLzWPc7Hq39VmFhDBEtW/79
npSkQy9LCepdAesTtQnHQcVQR1F2Sc+b+RTEagIUPywBVtV1tI0/6OX4RMxKjBAi
xcgQAOJuzFPxKDajPcBtg7wqoNfp+SRh5dSV2VHR1u/yJKpzMKxkQzurt/ai+Kek
XlOanLW9SmzCYOkkuEw2/J3BBqTn2vmZDm6xNN4HKH0hVibLgP2y5lEe+jtp7XwE
Lwn43E1xKJz2H+2FsVqW
=BLrR
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-03-30 18:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 12:58 [meta-oe] matching release branch for upcoming oe-core release Koen Kooi
2012-03-30 18:38 ` Koen Kooi [this message]
2012-03-30 19:04 ` Eric Bénard
2012-03-30 20:04 ` Koen Kooi
2012-03-30 21:51 ` Flanagan, Elizabeth
2012-03-30 22:10 ` Eric Bénard
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='jl4ui1$5d2$1@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--cc=openembedded-devel@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 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.