bitbake: doc/bitbake-user-manual-fetching: update the Git fetcher tag description

After commit d591d7633fe8 ("fetch/git: Rework tag parameter handling"),
update the description of the tag= parameter for the Git fetcher.

(Bitbake rev: 85b31a55d114a1430868233d56573b470fef8908)

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Antonin Godard
2025-07-22 13:41:27 +02:00
committed by Richard Purdie
parent b0f8af26a7
commit 92b07bd4ab

View File

@@ -439,10 +439,12 @@ This fetcher supports the following parameters:
- *"rev":* The revision to use for the checkout. If :term:`SRCREV` is also set, - *"rev":* The revision to use for the checkout. If :term:`SRCREV` is also set,
this parameter must match its value. this parameter must match its value.
- *"tag":* Specifies a tag to use for the checkout. To correctly - *"tag":* Specifies a tag to use when fetching. To correctly resolve
resolve tags, BitBake must access the network. For that reason, tags tags, BitBake must access the network. If a ``rev`` parameter or
are often not used. As far as Git is concerned, the "tag" parameter :term:`SRCREV` is also specified, network access is not necessary to resolve
behaves effectively the same as the "rev" parameter. the tag and instead, it is verified that they both resolve to the same commit
SHA at unpack time. The ``tag`` parameter is optional, but strongly
recommended if the checked out revision is a tag.
- *"subpath":* Limits the checkout to a specific subpath of the tree. - *"subpath":* Limits the checkout to a specific subpath of the tree.
By default, the whole tree is checked out. By default, the whole tree is checked out.