<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 30 July 2015 at 16:32, Alexander Kanavin <span dir="ltr"><<a href="mailto:alexander.kanavin@linux.intel.com" target="_blank">alexander.kanavin@linux.intel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">No, it contains only 219<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
-PV = "219-stable+git${SRCPV}"<br>
</blockquote></blockquote>
<br>
The idea here is that we only need the basic version, if the revision being fetched matches that version, and there is no need for all that git revision clutter in the version string.<br></blockquote></div><br>For the release tag I'd agree with you, but as 219 < 219-stable we can't just change this now (without adding an epoch, and adding epochs are evil).</div><div class="gmail_extra"><br></div><div class="gmail_extra">Does the RRS have a way of mapping a PV to something that can be used in the upstream comparison?</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>