From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH v3 0/2] pull request for twm and xclock recipes
Date: Fri, 07 Oct 2011 16:28:20 +0200 [thread overview]
Message-ID: <j6n2a4$gk6$1@dough.gmane.org> (raw)
In-Reply-To: <4E8F096F.5040003@mentor.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 07-10-11 16:15, Imran Mehmood schreef:
> hi koen, I will be thankful if you can kindly comment.
Please submit a new pull request, based on meta-oe with all the pending
mentor patches
>
> On 10/03/2011 05:48 PM, Imran Mehmood wrote:
>> hi koen,
>>
>> On 09/22/2011 11:57 AM, Koen Kooi wrote:
> Op 22-09-11 08:31, Mehmood, Imran schreef:
>>>>> From: Imran Mehmood<Imran_Mehmood@mentor.com>
>>>>>
>>>>> The following changes since commit
>>>>> 94a25d92b4d0e9379caaab127ccac1a94e9e4d28: Imran Mehmood (1):
>>>>> cramfs: Adds cvs version recipe (initial recipe)
> That isn't in meta-oe, so I can't pull your git tree. I'll grab the
> patches from patchwork for now, but in the future please use a clean tree
> for pull requests
>
>
>>> Sorry for much delayed response I was busy with some other issues. I
>>> fixed the warning messages with xclock but before sending the patch
>>> again just wanted to clear a confusion regarding your response
>>> below.
>>>
>>> I passed 94a25d92b4d0e9379caaab127ccac1a94e9e4d28 to
>>> create-pull-request script with -r because I wanted to create pull
>>> request for all commits on my branch, made after this one. If its
>>> wrong whats the right way or thing to do? I mean
>>>
>>> what commit id should I pass to the script? Please explain a bit more
>>> in detail so that I can prepare next patch as per requirements.
>>>
>>>
>>>
>>> _______________________________________________ Openembedded-devel
>>> mailing list Openembedded-devel@lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>>
>>
>>>
Thanks and Regards,
>> Imran Mehmood
>>
> Thanks and Regards, Imran Mehmood
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFOjwyEMkyGM64RGpERAo3SAJ0aha3/uqMgThPCNXGrQg0LKhrjMgCeOyKu
ygNNpWq6Uc2WOn/yf03POok=
=+t4w
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-10-07 14:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 6:31 [meta-oe][PATCH v3 0/2] pull request for twm and xclock recipes Mehmood, Imran
2011-09-22 6:31 ` [meta-oe][PATCH v2 1/2] xclock: Add version 1.0.5 (initial recipe) Mehmood, Imran
2011-09-22 7:30 ` Koen Kooi
2011-09-22 6:31 ` [meta-oe][PATCH v3 2/2] twm: Add version 1.0.6 " Mehmood, Imran
2011-09-22 7:30 ` Koen Kooi
2011-09-22 6:57 ` [meta-oe][PATCH v3 0/2] pull request for twm and xclock recipes Koen Kooi
2011-10-03 12:48 ` Imran Mehmood
2011-10-07 14:15 ` Imran Mehmood
2011-10-07 14:28 ` Koen Kooi [this message]
2011-10-07 14:30 ` Anders Darander
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='j6n2a4$gk6$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.