Subject: Error tagging: 2020-04.8-dunfell, 2020-04.8, and yocto-3.1.8 recreated To: openembedded-core@lists.openembedded.org From: "Michael Halstead" X-Originating-Location: Eugene, Oregon, US (24.21.216.192) X-Originating-Platform: Linux Chrome 91 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Wed, 02 Jun 2021 14:37:21 -0700 Message-ID: Content-Type: multipart/alternative; boundary="MvgdqEAXNatln2zq7K8B" --MvgdqEAXNatln2zq7K8B Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable During today's release three tags (2020-04.8-dunfell, 2020-04.8, and yocto-= 3.1.8) were made against the HEAD of the master branch instead of the corre= ct commit on the dunfell branch. The incorrect tags have been deleted and r= eplaced with the correct tags. A git force pull may be required to bring re= positories back into line. Please update your local repositories and ensure= any automated systems using the=C2=A0openembedded-core repo are functionin= g as expected. --MvgdqEAXNatln2zq7K8B Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable During today's release three tags (2020-04.8-dunfell, 2020-04.8, and yocto-= 3.1.8) were made against the HEAD of the master branch instead of the corre= ct commit on the dunfell branch. The incorrect tags have been deleted and r= eplaced with the correct tags. A git force pull may be required to bring re= positories back into line. Please update your local repositories and ensure= any automated systems using the openembedded-core repo are functionin= g as expected. --MvgdqEAXNatln2zq7K8B--