Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "Noor, Ahsan" <noor_ahsan@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-oe][PATCH v2 0/1] Pull request for python-lxml
Date: Mon,  5 Sep 2011 20:12:39 +0500	[thread overview]
Message-ID: <noor_ahsan@mentor.com> (raw)

From: Noor Ahsan <noor_ahsan@mentor.com>


The following changes since commit 6f1aa8626f859accef89c633aadaf13359bb1899:
  Noor Ahsan (1):
        Merge remote branch 'upstream/master'

are available in the git repository at:

  git://github.com/Noor-Ahsan/meta-oe master
  https://github.com/Noor-Ahsan/meta-oe/tree/master

Noor Ahsan (1):
  python-lxml: Add version  2.2.8 (initial recipe)

 .../recipes-devtools/python/python-lxml_2.2.8.bb   |   32 ++++++++++++++++++++
 1 files changed, 32 insertions(+), 0 deletions(-)
 create mode 100644 meta-oe/recipes-devtools/python/python-lxml_2.2.8.bb




             reply	other threads:[~2011-09-05 15:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-05 15:12 Noor, Ahsan [this message]
2011-09-05 15:12 ` [meta-oe][PATCH v2 1/1] python-lxml: Add version 2.2.8 (initial recipe) Noor, Ahsan
2011-09-05 18:52   ` Michael Lippautz
2011-09-06 12:18     ` Ahsan, Noor

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=noor_ahsan@mentor.com \
    --to=noor_ahsan@mentor.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