From: Paul Menzel <paulepanter@users.sourceforge.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH][meta-oe] python-lxml: Added new recipe in meta-oe for 2.2.8 version
Date: Mon, 29 Aug 2011 12:26:02 +0200 [thread overview]
Message-ID: <1314613573.6949.13.camel@mattotaupa> (raw)
In-Reply-To: <1313665760-21930-1-git-send-email-noor_ahsan@mentor.com>
[-- Attachment #1: Type: text/plain, Size: 1265 bytes --]
Dear Noor,
Am Donnerstag, den 18.08.2011, 16:09 +0500 schrieb Noor, Ahsan:
> From: Noor Ahsan <noor_ahsan@mentor.com>
>
> * Added new recipe in meta-oe for 2.2.8 version
I am sorry your patch has not gotten any review and has not been pushed
to meta-oe. It would be nice though, if you could take general comments
to your other patches and apply those to for example this patch.
1. Please update the commit summary.
2. Please remove the redundant line from the commit message’s body.
3. Please note that you got the recipe from oe.dev. I guess you did, did
not you?
(4. Include what build and run time environment you used for testing.)
5. Now that you have got the set up to send pull requests you can then
send that a version v2 with a pull request.
> Signed-off-by: Noor Ahsan <noor_ahsan@mentor.com>
With my comments addressed you can add
Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
to the commit message.
I am sorry that you have to resend it, but reviewing and writing
comments also takes a lot of time, people tend to not have a lot of.
Luckily Git (`git commit --amend` or `git rebase -i …`) makes it easy
for you to improve patches, so it only should take a few minutes.
Thanks,
Paul
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2011-08-29 10:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-18 11:09 [PATCH][meta-oe] python-lxml: Added new recipe in meta-oe for 2.2.8 version Noor, Ahsan
2011-08-29 8:38 ` Ahsan, Noor
2011-08-29 10:26 ` Paul Menzel [this message]
2011-08-29 10:29 ` 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=1314613573.6949.13.camel@mattotaupa \
--to=paulepanter@users.sourceforge.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.