From: "Peter Kjellerstedt" <peter.kjellerstedt@axis.com>
To: "Mittal, Anuj" <anuj.mittal@intel.com>,
"Tummalapalli, Vineela" <vineela.tummalapalli@intel.com>
Cc: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] [ANNOUNCEMENT] Yocto Project 3.2.1 (gatesgarth-24.0.1) is Released
Date: Wed, 23 Dec 2020 02:03:15 +0000 [thread overview]
Message-ID: <c2902cf4a4424fceb78b5da479d4012b@XBOX03.axis.com> (raw)
In-Reply-To: <b6efb453e252ef83fbad6c465ac834156d7f52fd.camel@intel.com>
> -----Original Message-----
> From: Mittal, Anuj <anuj.mittal@intel.com>
> Sent: den 22 december 2020 17:55
> To: Tummalapalli, Vineela <vineela.tummalapalli@intel.com>; Peter
> Kjellerstedt <peter.kjellerstedt@axis.com>
> Cc: yocto@lists.yoctoproject.org
> Subject: Re: [yocto] [ANNOUNCEMENT] Yocto Project 3.2.1 (gatesgarth-
> 24.0.1) is Released
>
> On Tue, 2020-12-15 at 23:07 +0000, Peter Kjellerstedt wrote:
> > > Repository Name: meta-gplv2
> > > Repository Location: https://git.yoctoproject.org/git/meta-gplv2
> > > Branch: gatesgarth
> > > Tag: yocto-3.2.1
> >
> > The yocto-3.2.1 and gatesgarth-24.0.1 tags for meta-gplv2 have been
> > incorrectly
> > set on the dunfell branch rather than the gatesgarth branch. The Git
> > revision
> > and tar balls below are correct though. Since the tags are signed I
> > do now want
> > to modify them myself, so please correct them as soon as possible.
>
> Vineela isn't working this week I think so she might not be able to
> help but it looks like the commit tagged is on gatesgarth ...
>
> https://git.yoctoproject.org/clean/cgit.cgi/meta-gplv2/log/?h=gatesgarth
>
> $ git branch -a --contains yocto-3.2.1
> * master
> remotes/origin/HEAD -> origin/master
> remotes/origin/gatesgarth
> remotes/origin/master
> remotes/origin/master-next
>
> Thanks,
>
> Anuj
You are absolutely correct. It seems the tags were incorrect for an hour
when first created, and apparently our local Git mirror does not handle
tags being updated so it still provides the original (incorrect) tags.
Thank you for pointing out what was a problem on our side. I will take
it up with our SCM team.
//Peter
next prev parent reply other threads:[~2020-12-23 2:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 21:13 [ANNOUNCEMENT] Yocto Project 3.2.1 (gatesgarth-24.0.1) is Released Vineela
2020-12-15 23:07 ` Peter Kjellerstedt
2020-12-22 16:54 ` [yocto] " Anuj Mittal
2020-12-23 2:03 ` Peter Kjellerstedt [this message]
[not found] ` <1651067E60B88465.19655@lists.yoctoproject.org>
2020-12-22 14:29 ` Peter Kjellerstedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c2902cf4a4424fceb78b5da479d4012b@XBOX03.axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=anuj.mittal@intel.com \
--cc=vineela.tummalapalli@intel.com \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox