<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jun 25, 2015 at 1:05 AM, Pierre-Yves Chibon <span dir="ltr"><<a href="mailto:pingou@pingoured.fr" target="_blank">pingou@pingoured.fr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div id=":1lo" class="" style="overflow:hidden">I think this is the core of our disagreement, many of the project we package are<br>
doing this. Ask Remi, he maintains several hundreds of packages and he can<br>
testify that this behavior is occurring also for projects that are packaged in<br>
Fedora and in other distributions.<br>
The fact that you find it hard to imagine is unfortunately not correlated with<br>
the fact that it occurs, also for projects we (as in Fedora) are interested in.</div></blockquote></div><br>I don't believe it is appropriate to throw the baby out with the bath water. </div><div class="gmail_extra">I've clarified that IF you believe a project is engaging in re-tagging you use</div><div class="gmail_extra">the commit hash method. Just because some projects are abusing a function </div><div class="gmail_extra">doesn't mean you issue a blanket ban. </div><div class="gmail_extra"><br></div><div class="gmail_extra">What my draft clarifies is that it is packagers decision on which method he wants<br></div><div class="gmail_extra">to use; and it describes a clear procedure that must be followed if upstream is </div><div class="gmail_extra">engaging in re-tagging. </div><div class="gmail_extra"><br></div><div class="gmail_extra"><div class="gmail_extra">If you wish to use the commit hash method all the time when dealing with Git,</div><div class="gmail_extra">you can. There is nothing in my text which says otherwise. </div></div></div>