But then looking at git itself, I don't see any mod to the old tag and the
new one looks OK.
Phil
On Fri, Sep 22, 2023 at 2:47 PM Phil Steitz wrote:
> This does not look good. I was following instructions in [1]. I just did
> git tag -s commons-pool2-2.12.0-rc2 -m "Tag Commons Pool release 2.12.0
> RC2"
>
> I don't think that tag already existed. Somehow it seems to have updated
> a 2.11.1 tag. Any suggestions on how to fix this?
>
> Phil
>
> [1]
> https://svn.apache.org/repos/infra/websites/production/commons/content/releases/prepare.html
>
>
> On Fri, Sep 22, 2023 at 2:39 PM wrote:
>
>> This is an automated email from the ASF dual-hosted git repository.
>>
>> psteitz pushed a change to annotated tag commons-pool2-2.12.0-rc2
>> in repository https://gitbox.apache.org/repos/asf/commons-pool.git
>>
>>
>> *** WARNING: tag commons-pool2-2.12.0-rc2 was modified! ***
>>
>> from ed218a61 (commit)
>> to 2abd33d4 (tag)
>> tagging ed218a61eaf2753dcd7aafbf050558b0a3550768 (commit)
>> replaces rel/commons-pool-2.11.1
>> by Phil Steitz
>> on Fri Sep 22 14:38:28 2023 -0700
>>
>> - Log -
>> Tag Commons Pool release 2.12.0 RC2
>> -BEGIN PGP SIGNATURE-
>> Comment: GPGTools - http://gpgtools.org
>>
>> iF0EABECAB0WIQROLd1H4Zhju4chFUTNMDj+8H1WfgUCZQ4JVAAKCRDNMDj+8H1W
>> fsCCAKCEuM/XzhGmu0hEVUgbPDya35eYoQCgmm310/yiLwKxE712XMtn6k66t68=
>> =hhDZ
>> -END PGP SIGNATURE-
>> ---
>>
>>
>> No new revisions were added by this update.
>>
>> Summary of changes:
>>
>>
