From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: bitbake-devel@lists.openembedded.org
Cc: docs@lists.yoctoproject.org,
Michael Opdenacker <michael.opdenacker@bootlin.com>
Subject: [PATCH 2/2] doc: bitbake-user-manual: branch parameter now mandatory in git SRC_URIs
Date: Wed, 9 Mar 2022 18:53:19 +0100 [thread overview]
Message-ID: <20220309175319.620707-2-michael.opdenacker@bootlin.com> (raw)
In-Reply-To: <20220309175319.620707-1-michael.opdenacker@bootlin.com>
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
doc/bitbake-user-manual/bitbake-user-manual-fetching.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/bitbake-user-manual/bitbake-user-manual-fetching.rst b/doc/bitbake-user-manual/bitbake-user-manual-fetching.rst
index ae2d3a17..d0c78062 100644
--- a/doc/bitbake-user-manual/bitbake-user-manual-fetching.rst
+++ b/doc/bitbake-user-manual/bitbake-user-manual-fetching.rst
@@ -432,8 +432,8 @@ This fetcher supports the following parameters:
raw Git metadata is provided. This parameter implies the "nocheckout"
parameter as well.
-- *"branch":* The branch(es) of the Git tree to clone. If unset, this
- is assumed to be "master". The number of branch parameters much match
+- *"branch":* The branch(es) of the Git tree to clone. This is a
+ mandatory parameter. The number of branch parameters must match
the number of name parameters.
- *"rev":* The revision to use for the checkout. The default is
--
2.25.1
next prev parent reply other threads:[~2022-03-09 17:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 17:53 [PATCH 1/2] doc: bitbake-user-manual: add branch parameter to git SRC_URI examples Michael Opdenacker
2022-03-09 17:53 ` Michael Opdenacker [this message]
2022-03-10 10:53 ` [docs] [PATCH 2/2] doc: bitbake-user-manual: branch parameter now mandatory in git SRC_URIs Peter Kjellerstedt
2022-03-10 16:38 ` Michael Opdenacker
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=20220309175319.620707-2-michael.opdenacker@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=docs@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 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.