From: <liezhi.yang@windriver.com>
To: <bitbake-devel@lists.openembedded.org>
Subject: [PATCH 0/1] fetch2/git.py: Try without '.git' suffix firstly
Date: Wed, 15 May 2024 02:26:36 -0700 [thread overview]
Message-ID: <cover.1715765153.git.liezhi.yang@windriver.com> (raw)
From: Robert Yang <liezhi.yang@windriver.com>
The following changes since commit 79ab2413e082838291157445038476f9d8edb586:
cpio: mark CVE-2023-7216 as disputed (2024-05-14 12:43:23 +0100)
are available in the Git repository at:
https://github.com/robertlinux/yocto rbt/fetch
https://github.com/robertlinux/yocto/tree/rbt/fetch
Robert Yang (1):
fetch2/git.py: Try without '.git' suffix firstly
bitbake/lib/bb/fetch2/git.py | 23 +++++++++++++++++++++--
1 file changed, 21 insertions(+), 2 deletions(-)
--
2.35.5
next reply other threads:[~2024-05-15 9:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 9:26 liezhi.yang [this message]
2024-05-15 9:26 ` [PATCH 1/1] fetch2/git.py: Try without '.git' suffix firstly liezhi.yang
2024-05-15 9:35 ` [bitbake-devel] " Quentin Schulz
2024-05-15 9:57 ` Robert Yang
2024-05-15 10:15 ` Quentin Schulz
2024-05-15 15:47 ` Richard Purdie
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=cover.1715765153.git.liezhi.yang@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=bitbake-devel@lists.openembedded.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).