From: "Anuj Mittal" <anuj.mittal@intel.com>
To: "Tummalapalli, Vineela" <vineela.tummalapalli@intel.com>,
"peter.kjellerstedt@axis.com" <peter.kjellerstedt@axis.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: Tue, 22 Dec 2020 16:54:58 +0000 [thread overview]
Message-ID: <b6efb453e252ef83fbad6c465ac834156d7f52fd.camel@intel.com> (raw)
In-Reply-To: <fcdceff7753a4f52911b8b3c61a35d76@XBOX03.axis.com>
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
next prev parent reply other threads:[~2020-12-22 16:55 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 ` Anuj Mittal [this message]
2020-12-23 2:03 ` [yocto] " Peter Kjellerstedt
[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=b6efb453e252ef83fbad6c465ac834156d7f52fd.camel@intel.com \
--to=anuj.mittal@intel.com \
--cc=peter.kjellerstedt@axis.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