Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Armin Kuster <akuster808@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] Dizzy-next merge request
Date: Wed,  3 Dec 2014 11:38:01 -0800	[thread overview]
Message-ID: <cover.1417635272.git.akuster808@gmail.com> (raw)

one more merge

The following changes since commit be128c799489b95b740f2803c16e047a1f307781:

  gst-ffmpeg: fixes for CVE-2014-8548 and CVE-2014-8541 (2014-12-03 08:01:28 -0800)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib akuster/dizzy-next
  http://git.yoctoproject.org/cgit.cgi//log/?h=akuster/dizzy-next

He Zhe (1):
  kernel.bbclass: Create modules directory even if there is no modules
    installed

 meta/classes/kernel.bbclass | 1 +
 1 file changed, 1 insertion(+)

-- 
1.9.1



             reply	other threads:[~2014-12-03 19:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-03 19:38 Armin Kuster [this message]
2014-12-03 19:38 ` [PATCH 1/1] kernel.bbclass: Create modules directory even if there is no modules installed Armin Kuster

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=cover.1417635272.git.akuster808@gmail.com \
    --to=akuster808@gmail.com \
    --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