On 04/19/2016 10:31 PM, Christoph Berg wrote:
> Re: Sebastiaan Couwenberg 2016-04-19 <571694F9.6040400@xs4all.nl>
>>> So I need to name the tag 2.2.1 to be 2.2.2
>>> and recover the hash from 2.2.1 and tag it again, is that correct?
>>
>> Yes, ideally the old 2.2.1 tag is restored to reference the old commit,
>> and the new 2.2.1 tag needs to be replaced with 2.2.2, but you'll likely
>> need to change a couple of source files to use 2.2.2 first too.
>
> Hmm, doesn't that create the same problem the other way round for the
> other half of the world that has downloaded the newer tarball?
>
> From what I understood, the difference was just changelog/news, so
> wouldn't just waiting for the next release to happen eventually be
> good enough?
Yes, it does. This just underscore the issue of changing tags after
they've been published outside your local repository.
So please disregard my advise to change the 2.2.1 tag, just make sure
2.2.2 gets it right.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
