From: Tom Rini <trini@konsulko.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>,
Oleksandr Kravchuk <open.source@oleksandr-kravchuk.com>
Subject: Re: [PATCH v2] vim: update to 8.1.1097
Date: Sun, 31 Mar 2019 16:56:13 -0400 [thread overview]
Message-ID: <20190331205613.GA4664@bill-the-cat> (raw)
In-Reply-To: <CANNYZj9QeaLU8AC03CmtczcVJ_jbuaL7gQEQ6HQVnDB82z+taw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 903 bytes --]
On Sun, Mar 31, 2019 at 10:19:51PM +0200, Alexander Kanavin wrote:
> On Sun, 31 Mar 2019 at 22:12, Tom Rini <trini@konsulko.com> wrote:
> > 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.
>
> It's a bit insane upstream is doing that.
> Should we set PV to something like PV = "8.1+git${SRCPV}"? That way
> devtool/AUH/RRS will not be reporting a new version for each commit,
> and will only do that when 8.2 is out.
No, we should follow what upstream does for version numbers, it's what
other distros do. And on the related topic of "is it a stable branch?",
it does seem like yes, it is. We should just remember to not update it
more often than say the first of the month, without a specific reason.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2019-03-31 20:56 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
2019-03-31 20:19 ` Alexander Kanavin
2019-03-31 20:56 ` Tom Rini [this message]
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=20190331205613.GA4664@bill-the-cat \
--to=trini@konsulko.com \
--cc=alex.kanavin@gmail.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 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.