aboutsummaryrefslogtreecommitdiffstats
path: root/vendor/libghostty-vt/src/terminal/c/result.zig
diff options
context:
space:
mode:
authoruser <user@clank>2026-09-02 15:38:38 +0200
committeruser <user@clank>2026-09-02 15:38:38 +0200
commit8c1553801a9812bf4e8541872eb720470ce89a0b (patch)
treeb98235789fc5c54d135a6d08ecf7361fdcdf1197 /vendor/libghostty-vt/src/terminal/c/result.zig
parentarch-repo: find zig on PATH itself; release: v0.1.3 paperwork (diff)
downloadslosh-8c1553801a9812bf4e8541872eb720470ce89a0b.tar.gz
slosh-8c1553801a9812bf4e8541872eb720470ce89a0b.tar.xz
slosh-8c1553801a9812bf4e8541872eb720470ce89a0b.zip
contrib/vendor-check: watching upstream is one command now
Vendoring by pinned commit stays (D12) -- the package channels build from source archives where submodules are empty, the arch build is offline-clean because the core is in the tarball, and upstream has no stable release channel to depend on anyway. What was missing is the watching: vendor-check reads the pin from vendor.json, asks the GitHub API what happened since, and lists the commits touching the terminal core. First run found 120 relevant commits in three weeks, including upstream fixing the same class of kitty-graphics bug our patch 0001 fixes -- which is the argument for finally sending it.
Diffstat (limited to 'vendor/libghostty-vt/src/terminal/c/result.zig')
0 files changed, 0 insertions, 0 deletions