From: Radu Moisan <radu.moisan@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/3] mtd-utils: Update to version 1.5.0
Date: Fri, 25 May 2012 12:30:41 +0300 [thread overview]
Message-ID: <4FBF5141.1070908@intel.com> (raw)
In-Reply-To: <20120525085103.GB3138@jama.jama.net>
[-- Attachment #1: Type: text/plain, Size: 2410 bytes --]
your're right, I'll prepare a new patch for that.
Thanks,
Radu
On 05/25/2012 11:51 AM, Martin Jansa wrote:
> On Fri, May 25, 2012 at 11:50:56AM +0300, Radu Moisan wrote:
>> Signed-off-by: Radu Moisan<radu.moisan@intel.com>
>> ---
>> .../add-exclusion-to-mkfs-jffs2-git-2.patch | 0
>> .../mtd/{mtd-utils_1.4.9.bb => mtd-utils_1.5.0.bb} | 2 +-
>> 2 files changed, 1 insertion(+), 1 deletion(-)
>> rename meta/recipes-devtools/mtd/{mtd-utils-1.4.9 => mtd-utils-1.5.0}/add-exclusion-to-mkfs-jffs2-git-2.patch (100%)
>> rename meta/recipes-devtools/mtd/{mtd-utils_1.4.9.bb => mtd-utils_1.5.0.bb} (98%)
>>
>> diff --git a/meta/recipes-devtools/mtd/mtd-utils-1.4.9/add-exclusion-to-mkfs-jffs2-git-2.patch b/meta/recipes-devtools/mtd/mtd-utils-1.5.0/add-exclusion-to-mkfs-jffs2-git-2.patch
>> similarity index 100%
>> rename from meta/recipes-devtools/mtd/mtd-utils-1.4.9/add-exclusion-to-mkfs-jffs2-git-2.patch
>> rename to meta/recipes-devtools/mtd/mtd-utils-1.5.0/add-exclusion-to-mkfs-jffs2-git-2.patch
>> diff --git a/meta/recipes-devtools/mtd/mtd-utils_1.4.9.bb b/meta/recipes-devtools/mtd/mtd-utils_1.5.0.bb
>> similarity index 98%
>> rename from meta/recipes-devtools/mtd/mtd-utils_1.4.9.bb
>> rename to meta/recipes-devtools/mtd/mtd-utils_1.5.0.bb
>> index 4228b51..be71efe 100644
>> --- a/meta/recipes-devtools/mtd/mtd-utils_1.4.9.bb
>> +++ b/meta/recipes-devtools/mtd/mtd-utils_1.5.0.bb
>> @@ -11,7 +11,7 @@ SRC_URI = "git://git.infradead.org/mtd-utils.git;protocol=git;tag=995cfe51b0a3cf
>>
>> S = "${WORKDIR}/git/"
>>
>> -PR = "r1"
>> +PR = "r0"
>>
>> EXTRA_OEMAKE = "'CC=${CC}' 'RANLIB=${RANLIB}' 'AR=${AR}' 'CFLAGS=${CFLAGS} -I${S}/include -DWITHOUT_XATTR' 'BUILDDIR=${S}'"
> does it really update version?
> SRC_URI = "git://git.infradead.org/mtd-utils.git;protocol=git;tag=995cfe51b0a3cf32f381c140bf72b21bf91cef1b
> wasn't changed, so I guess the sources are the same.
>
> Cheers,
>
>>
>> --
>> 1.7.9.5
>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[-- Attachment #2: Type: text/html, Size: 3466 bytes --]
next prev parent reply other threads:[~2012-05-25 9:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 8:50 [PATCH 0/3] Package Updates Radu Moisan
2012-05-25 8:50 ` [PATCH 1/3] foomatic-filters: update to version 4.0.15 Radu Moisan
2012-05-30 12:03 ` Richard Purdie
2012-05-25 8:50 ` [PATCH 2/3] mtd-utils: Update to version 1.5.0 Radu Moisan
2012-05-25 8:51 ` Martin Jansa
2012-05-25 9:30 ` Radu Moisan [this message]
2012-05-25 9:41 ` Radu Moisan
2012-05-25 9:42 ` Andrei Gherzan
2012-05-25 8:50 ` [PATCH 3/3] dbus: Update to version 1.5.12 Radu Moisan
2012-05-25 9:52 ` [PATCH 0/3] Package Updates Koen Kooi
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=4FBF5141.1070908@intel.com \
--to=radu.moisan@intel.com \
--cc=openembedded-core@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.