From: <liezhi.yang@windriver.com>
To: <bitbake-devel@lists.openembedded.org>
Subject: [PATCH 0/1] fetch2/git: Use basename for gitsrcname when ud.proto is file
Date: Fri, 21 Jun 2024 22:20:06 -0700 [thread overview]
Message-ID: <cover.1719033434.git.liezhi.yang@windriver.com> (raw)
From: Robert Yang <liezhi.yang@windriver.com>
* Test info
- bitbake world --runall=fetch works well when BB_GENERATE_MIRROR_TARBALLS
and BB_GIT_SHALLOW are enabled or disabled
- bitbake-selftest works well
// Robert
The following changes since commit 5d88faa0f35f0205c1475893d8589d1e6533dcc0:
bitbake: siggen: catch FileNotFoundError everywhere and ConnectionError also in get_unihashes (2024-06-18 08:45:22 +0100)
are available in the Git repository at:
https://github.com/robertlinux/yocto rbt/fetch_git
https://github.com/robertlinux/yocto/tree/rbt/fetch_git
Robert Yang (1):
fetch2/git: Use basename for gitsrcname when ud.proto is file
bitbake/lib/bb/fetch2/git.py | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
--
2.45.1
next reply other threads:[~2024-06-22 5:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-22 5:20 liezhi.yang [this message]
2024-06-22 5:20 ` [PATCH 1/1] fetch2/git: Use basename for gitsrcname when ud.proto is file liezhi.yang
2024-07-14 11:17 ` [bitbake-devel] " Richard Purdie
2024-07-14 13:03 ` Robert Yang
2024-07-14 13:32 ` Richard Purdie
2024-07-14 13:54 ` Robert Yang
2024-08-06 11:06 ` Richard Purdie
2024-08-06 11:20 ` Ross Burton
2024-08-06 13:42 ` Robert Yang
2024-08-06 14:10 ` Richard Purdie
2024-08-07 2:23 ` Robert Yang
2024-08-07 14:58 ` Richard Purdie
[not found] ` <17E927848AD479BA.28314@lists.openembedded.org>
2024-08-06 13:50 ` Robert Yang
2024-07-14 11:08 ` [bitbake-devel] [PATCH 0/1] " Robert Yang
2025-05-12 9:26 ` Yi Qingliang
2025-05-12 11:20 ` [bitbake-devel] " Koch, Stefan
2025-05-13 0:41 ` Yi Qingliang
2025-05-13 0:48 ` Yi Qingliang
2025-05-13 1:02 ` Yi Qingliang
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.1719033434.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.