From: <Mikko.Rapeli@bmw.de>
To: <alex.kanavin@gmail.com>
Cc: <Martin.Jansa@gmail.com>, <bitbake-devel@lists.openembedded.org>,
<marex@denx.de>, <peter.kjellerstedt@axis.com>,
<richard.purdie@linuxfoundation.org>
Subject: Re: [bitbake-devel] [PATCH] [RFC] fetch2/git: Prevent git fetcher from fetching gitlab repository metadata
Date: Mon, 22 Aug 2022 07:38:08 +0000 [thread overview]
Message-ID: <YwMyXi/vfRh3S6bx@korppu> (raw)
In-Reply-To: <CANNYZj_Ag2Y8ZTXVgwagGv+26+HKPM31SRq8p3h4EL0PUEPefQ@mail.gmail.com>
On Mon, Aug 22, 2022 at 08:57:11AM +0200, Alexander Kanavin wrote:
> Can be solved with a parameter to a fetcher perhaps?
Frequently developers know to change the git URL in recipes from
"branch=master" to "nobranch=1" for their test commits.
This could be used for fetching the changes too, to limit the scope.
Cheers,
-Mikko
next prev parent reply other threads:[~2022-08-22 7:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 16:54 [PATCH] [RFC] fetch2/git: Prevent git fetcher from fetching gitlab repository metadata Marek Vasut
2022-08-20 12:06 ` Peter Kjellerstedt
2022-08-22 5:19 ` [bitbake-devel] " Mikko.Rapeli
2022-08-22 6:57 ` Alexander Kanavin
2022-08-22 7:38 ` Mikko.Rapeli [this message]
2022-08-22 8:29 ` Marek Vasut
2022-08-22 8:37 ` Marek Vasut
2022-08-22 8:41 ` Marek Vasut
2022-08-22 9:09 ` Mikko.Rapeli
2022-08-22 8:41 ` Alexander Kanavin
2022-08-22 10:35 ` Marek Vasut
2022-08-22 10:51 ` Mikko.Rapeli
2022-08-22 10:57 ` Quentin Schulz
2022-08-22 11:55 ` Marek Vasut
2022-08-22 14:17 ` Richard Purdie
2022-08-22 15:21 ` Peter Kjellerstedt
2022-08-22 16:39 ` Marek Vasut
2022-09-01 17:50 ` Marek Vasut
2022-09-02 15:54 ` Richard Purdie
2022-08-22 16:02 ` Luca Ceresoli
2022-08-22 16:06 ` Peter Kjellerstedt
2022-08-22 16:07 ` Richard Purdie
2022-08-23 14:34 ` Luca Ceresoli
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=YwMyXi/vfRh3S6bx@korppu \
--to=mikko.rapeli@bmw.de \
--cc=Martin.Jansa@gmail.com \
--cc=alex.kanavin@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=marex@denx.de \
--cc=peter.kjellerstedt@axis.com \
--cc=richard.purdie@linuxfoundation.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.