On Fri, Jun 26, 2015 at 9:18 AM, Remi Collet <Fedora@famillecollet.com> wrote:
This is exactly what I named "last solution".

Your proposal switch the Guidelines from
        "must use hash commit"

to      "could use hash commit if no other solution exists,
        but really you should try something else before"
First of all, the current guidelines do not say that you must use commit hash, and
my text doesn't at all say what you're implying.  You're reading in something that
simply isn't there.

It would be helpful if you could answer the questions I previously asked.  Here 
they are again:

Why are you so concerned about the use of Git Tags?  I have included text 
which clearly states that if the packager believes that re-tagging is being used, 
he MUST follow a specific procedure to resolve that issue.  

If there is a problem with the archive the checksum 
won't match.  The archive with the embedded commit information is already in the srpm.  
The act of re-tagging can't change that.  We always know the commit hash
version of that archive.  What is the harm if we later find that upstream did re-tag?