mirror of
https://github.com/openglow-org/forgefirm.git
synced 2026-09-27 08:41:13 -07:00
ScottW514
722de73a39
The three components carry documentation-only commits: the README becomes an index card, AGENTS.md lands, and the comments that pointed at the retired BRINGUP.md now point at the documentation site. The pins move because the tree is already past the image that 20260907224817 built: a comment in the kernel config fragment glowforge.cfg changed the meta-glowforge-bsp layer content hash, which the manifest counts as a platform change. Measured against that image's manifest: meta-forgefirm and meta-openglow-core are unchanged, meta-glowforge-bsp is not. A fresh image build and a full acceptance campaign therefore precede any release, and holding these pins back would buy nothing. Verified: every pinned revision is on its public remote, and bitbake -c fetch resolves all of them.
7 lines
337 B
PHP
7 lines
337 B
PHP
# forgectrl pin. Bump deliberately after pushing forgectrl changes; keep
|
|
# only SRCREV and PV here - the image manifest leaves *-pin.inc out of the
|
|
# layer content hash because the component entry already identifies the
|
|
# pinned source (forgefirm-image-manifest.bbclass).
|
|
SRCREV = "692e4d8ff689d6752b347ca8cc0202f9ad63a320"
|
|
PV = "0.1.7"
|