From: Felipe Correa da Silva Sanches Date: Fri, 24 Apr 2026 09:19:46 +0000 (+0100) Subject: Namdhinggo: add override config.yaml (compatible upstream sources) X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=3bdc6ce2fbe93ea23e2ee668a436207e5c730279;p=thirdparty%2Fgoogle%2Ffonts.git Namdhinggo: add override config.yaml (compatible upstream sources) - Repo: silnrsi/font-namdhinggo - Commit: 2c6ac797b061941d1f46c980910982b1b1f240ab (unchanged) - Config: override in ofl/namdhinggo/config.yaml - Status: complete - Confidence: HIGH Upstream has a .designspace sources at the pinned commit but no config file. An override was added referencing source/Namdhinggo.designspace. STAT values omitted — gftools-builder will auto-derive. Assisted by an AI agent (Claude Opus 4.7 1M context) --- diff --git a/ofl/namdhinggo/config.yaml b/ofl/namdhinggo/config.yaml new file mode 100644 index 000000000..35a83a208 --- /dev/null +++ b/ofl/namdhinggo/config.yaml @@ -0,0 +1,4 @@ +sources: + - source/Namdhinggo.designspace +familyName: "Namdhinggo" +buildVariable: false diff --git a/ofl/namdhinggo/upstream_info.md b/ofl/namdhinggo/upstream_info.md index 1418066c3..57c8fbe17 100644 --- a/ofl/namdhinggo/upstream_info.md +++ b/ofl/namdhinggo/upstream_info.md @@ -55,3 +55,9 @@ Without local access to the `font-namdhinggo` repo, the exact source format cann ## Commit Added (HIGH confidence) Commit `2c6ac797b061941d1f46c980910982b1b1f240ab` was determined by **tag_match**. Matched a version tag in the upstream repo whose date is on or before the binary modification date in google/fonts (2023-07-06). This is the most reliable method. + +## Update (2026-04-24) — Override config.yaml + +**Model**: Claude Opus 4.7 (1M context) + +Added an override `config.yaml` in `ofl/namdhinggo/` referencing the upstream gftools-builder-compatible source at the pinned commit `2c6ac79` (`source/Namdhinggo.designspace`). The upstream repo has no `config.yaml` of its own at this rev; `google-fonts-sources` auto-detects the override and records it in crater's `targets.json` as an external config on the next regeneration.