<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 1/14/20 5:18 PM, Alexander Kanavin
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CANNYZj83UugdN=aNFncqFRF304YxBtYLgd6b4bP-Na_bLvMvwA@mail.gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">On Tue, 14 Jan 2020 at 21:10, Randy MacLeod <<a
href="mailto:randy.macleod@windriver.com"
moz-do-not-send="true">randy.macleod@windriver.com</a>>
wrote:<br>
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">Oleg is getting started
using Yocto so I'll reply on his behalf since<br>
I asked him to update vim as his first commit.<br>
<br>
I'm not sure what you mean by 8.2. Are you talking about
calling the recipe:<br>
<a href="http://vim_8.2.bb" rel="noreferrer"
target="_blank" moz-do-not-send="true">vim_8.2.bb</a><br>
instead of <a href="http://vim_8.2.0110.bb"
rel="noreferrer" target="_blank" moz-do-not-send="true">vim_8.2.0110.bb</a>?<br>
<br>
Vim tags on a daily or more frequent basis. Are you saying
that we <br>
should keep the<br>
same SRCREV for 8.2.0110 but use a different name?<br>
<br>
I looked at:<br>
git log v8.2.0000..v8.2.0118<br>
and all the commits seem to fix bugs so I prefer to take
this tested <br>
v8.2.0110<br>
update and update vim every month or two so that we get the
latest fixes.<br>
</blockquote>
<div><br>
</div>
<div>Vim adds a tag for every single commit they make, fixes
or not, so this approach would in effect be updating to
random development snapshots. I would rather have a more
conservative update strategy, and update to the original 8.2
release. If you look at the homepage, 8.2 is the version
they announced as the new release: <a
href="https://www.vim.org/" moz-do-not-send="true">https://www.vim.org/</a></div>
</div>
</div>
</blockquote>
<p><br>
</p>
<p>Sure, that's fine for now. Most of the commits are bug fixes
after 8.2 but we don't need to<br>
worry about any of them now and I guess if we stick with this
approach, and say there as<br>
a CVE for vim that we wanted to fix, we'd just backport the single
commit rather than<br>
bump the version to 8.2.1248 or some such version.<br>
</p>
<blockquote type="cite"
cite="mid:CANNYZj83UugdN=aNFncqFRF304YxBtYLgd6b4bP-Na_bLvMvwA@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<div><br>
</div>
<div>That's also what 'devtool latest-version vim' should
currently report and 'devtool upgrade' upgrade to: I
purposely cut off the point releases and left only the
major.minor part there.<br>
</div>
</div>
</div>
</blockquote>
<p>Right. This will also give Oleg an excuse to try 'devtool
upgrade' to compare manually upgrading. :)</p>
<p>../Randy</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:CANNYZj83UugdN=aNFncqFRF304YxBtYLgd6b4bP-Na_bLvMvwA@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<div><br>
</div>
<div>Alex<br>
</div>
</div>
</div>
</blockquote>
<p><br>
</p>
<pre class="moz-signature" cols="72">--
# Randy MacLeod
# Wind River Linux
</pre>
</body>
</html>