Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-oe] [PATCHv2 0/1] Pull request #6
Date: Thu, 14 Apr 2011 08:46:02 +0200	[thread overview]
Message-ID: <cover.1302763397.git.Martin.Jansa@gmail.com> (raw)

Small fix for mesa-xlib.
FILESPATHPKG support in oe-core would be nice.

Pull URL: git://gitorious.org/shr/meta-openembedded.git
  Branch: jama/meta-oe
  Browse: http://gitorious.org/shr/meta-openembedded/commits/jama/meta-oe

Thanks,
    Martin Jansa <Martin.Jansa@gmail.com>
---


Martin Jansa (1):
  mesa-xlib: fix FILESPATH

 meta-oe/recipes-graphics/mesa/mesa-xlib.inc |    5 ++++-
 1 files changed, 4 insertions(+), 1 deletions(-)

-- 
1.7.5.rc1




             reply	other threads:[~2011-04-14  6:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-14  6:46 Martin Jansa [this message]
2011-04-14  6:46 ` [PATCHv2 1/1] mesa-xlib: fix FILESPATH Martin Jansa
2011-04-16 11:01 ` [meta-oe] [PATCHv2 0/1] Pull request #6 Koen Kooi
2011-04-16 11:56   ` Martin Jansa

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.1302763397.git.Martin.Jansa@gmail.com \
    --to=martin.jansa@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox