<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 4 July 2016 at 14:18, Khem Raj <span dir="ltr"><<a href="mailto:raj.khem@gmail.com" target="_blank">raj.khem@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":grl" class="a3s aXjCH m155b610313e8dd7f">we do not do that for recipes with git fetchers usually. PV is encoded<br>
as PV+git{SRCPV}</div></blockquote></div><br>For recipes which are tracking releases, it's fairly common - and I feel clearer - use have the PV in the filename and thus PV instead of spreading the SHA everywhere for no reason. It's version 0.6.22, nobody cares what the SHA is.</div><div class="gmail_extra"><br></div><div class="gmail_extra">*If* it was a SHA beyond 0.6.22 then PV+SHA makes perfect sense.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>