From: Robert Yang <liezhi.yang@windriver.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/4] python-git: upgrade to 0.3.3
Date: Fri, 9 Jan 2015 19:15:02 +0800 [thread overview]
Message-ID: <54AFB836.5000506@windriver.com> (raw)
In-Reply-To: <2550081.xQ1aUrNKGO@peggleto-mobl5.ger.corp.intel.com>
On 01/09/2015 06:33 PM, Paul Eggleton wrote:
> Hi Robert,
>
> On Thursday 08 January 2015 21:33:39 Robert Yang wrote:
>> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
>> ---
>> ...python-git_0.3.2.RC1.bb => python-git_0.3.3.bb} | 5 +++--
>> 1 file changed, 3 insertions(+), 2 deletions(-)
>> rename meta/recipes-devtools/python/{python-git_0.3.2.RC1.bb =>
>> python-git_0.3.3.bb} (85%)
>>
>> diff --git a/meta/recipes-devtools/python/python-git_0.3.2.RC1.bb
>> b/meta/recipes-devtools/python/python-git_0.3.3.bb similarity index 85%
>> rename from meta/recipes-devtools/python/python-git_0.3.2.RC1.bb
>> rename to meta/recipes-devtools/python/python-git_0.3.3.bb
>> index 02a0eac..860c37b 100644
>> --- a/meta/recipes-devtools/python/python-git_0.3.2.RC1.bb
>> +++ b/meta/recipes-devtools/python/python-git_0.3.3.bb
>> @@ -10,8 +10,9 @@ LIC_FILES_CHKSUM =
>> "file://LICENSE;md5=8b8d26c37c1d5a04f9b0186edbebc183" DEPENDS =
>> "python-gitdb"
>>
>> SRC_URI =
>> "http://pypi.python.org/packages/source/G/GitPython/GitPython-${PV}.tar.gz"
>> -SRC_URI[md5sum] = "849082fe29adc653a3621465213cab96"
>> -SRC_URI[sha256sum] =
>> "fd6786684a0d0dd7ebb961da754e3312fafe0c8e88f55ceb09858aa0af6094e0" +
>> +SRC_URI[md5sum] = "c9fdde02c476c11168fd620659496aba"
>> +SRC_URI[sha256sum] =
>> "08193acf4e22b57a471cde3748ebce7c17e0f15f1e5042db74ca2c5e9e3e4db5"
>>
>> S = "${WORKDIR}/GitPython-${PV}"
>
> Interesting, I didn't expect this project to have come back alive again
> upstream, as earlier it looked like it was considered deprecated in favour of
> pygit2. Thanks for taking care of the upgrade.
You're welcome, I saw that it was not in maintainers.inc, and I have
interests on it, so I took it and upgraded.
// Robert
>
> Cheers,
> Paul
>
next prev parent reply other threads:[~2015-01-09 11:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 5:33 [PATCH 0/4] Ugrade binutils, gnu-efi, python-git and python-gitdb Robert Yang
2015-01-09 5:33 ` [PATCH 1/4] python-git: upgrade to 0.3.3 Robert Yang
2015-01-09 10:33 ` Paul Eggleton
2015-01-09 11:15 ` Robert Yang [this message]
2015-01-09 5:33 ` [PATCH 2/4] python-gitdb: upgrade to 0.6.1 Robert Yang
2015-01-09 5:33 ` [PATCH 3/4] gnu-efi: upgrade to 3.0.1 Robert Yang
2015-01-09 17:20 ` Burton, Ross
2015-01-11 1:56 ` Robert Yang
2015-01-09 5:33 ` [PATCH 4/4] binutils: upgrade to 2.24 Robert Yang
2015-01-09 5:39 ` Khem Raj
2015-01-09 6:00 ` Robert Yang
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=54AFB836.5000506@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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