From: Tom Rini <trini@konsulko.com>
To: Oleksandr Kravchuk <open.source@oleksandr-kravchuk.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] vim: update to 8.1.1097
Date: Sun, 31 Mar 2019 16:11:41 -0400 [thread overview]
Message-ID: <20190331201141.GH18421@bill-the-cat> (raw)
In-Reply-To: <20190331155012.3085-1-open.source@oleksandr-kravchuk.com>
[-- Attachment #1: Type: text/plain, Size: 1759 bytes --]
On Sun, Mar 31, 2019 at 05:50:12PM +0200, Oleksandr Kravchuk wrote:
> Signed-off-by: Oleksandr Kravchuk <open.source@oleksandr-kravchuk.com>
> ---
> .../vim/{vim-tiny_8.1.1017.bb => vim-tiny_8.1.1097.bb} | 0
> meta/recipes-support/vim/{vim_8.1.1017.bb => vim_8.1.1097.bb} | 2 +-
> 2 files changed, 1 insertion(+), 1 deletion(-)
> rename meta/recipes-support/vim/{vim-tiny_8.1.1017.bb => vim-tiny_8.1.1097.bb} (100%)
> rename meta/recipes-support/vim/{vim_8.1.1017.bb => vim_8.1.1097.bb} (98%)
>
> diff --git a/meta/recipes-support/vim/vim-tiny_8.1.1017.bb b/meta/recipes-support/vim/vim-tiny_8.1.1097.bb
> similarity index 100%
> rename from meta/recipes-support/vim/vim-tiny_8.1.1017.bb
> rename to meta/recipes-support/vim/vim-tiny_8.1.1097.bb
> diff --git a/meta/recipes-support/vim/vim_8.1.1017.bb b/meta/recipes-support/vim/vim_8.1.1097.bb
> similarity index 98%
> rename from meta/recipes-support/vim/vim_8.1.1017.bb
> rename to meta/recipes-support/vim/vim_8.1.1097.bb
> index 7627d2844b..4de1bc3807 100644
> --- a/meta/recipes-support/vim/vim_8.1.1017.bb
> +++ b/meta/recipes-support/vim/vim_8.1.1097.bb
> @@ -13,7 +13,7 @@ SRC_URI = "git://github.com/vim/vim.git \
> file://vim-add-knob-whether-elf.h-are-checked.patch;patchdir=.. \
> file://0001-src-Makefile-improve-reproducibility.patch;patchdir=.. \
> "
> -SRCREV = "493fbe4abee660d30b4f2aef87b754b0a720213c"
> +SRCREV = "4fc8e2f8bb3eb42df0f72cfcc1f8f8e567e7ce4f"
>
> S = "${WORKDIR}/git/src"
Looks better, thanks. Is there a particular fix / change you're doing
this for? I ask since every commit is a version bump we might want to
set a guideline of once a month or so for bumping vim to the latest.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2019-03-31 20:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-31 15:50 [PATCH v2] vim: update to 8.1.1097 Oleksandr Kravchuk
2019-03-31 20:11 ` Tom Rini [this message]
2019-03-31 20:19 ` Alexander Kanavin
2019-03-31 20:56 ` Tom Rini
2019-03-31 22:28 ` Paul Barker
2019-03-31 22:31 ` Tom Rini
2019-04-01 0:14 ` Oleksandr Kravchuk
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=20190331201141.GH18421@bill-the-cat \
--to=trini@konsulko.com \
--cc=open.source@oleksandr-kravchuk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox