From 68f63858702015f8994b9c3413708e08ed4693e7 Mon Sep 17 00:00:00 2001 From: Tommaso Negri Date: Tue, 11 Aug 2026 14:18:06 +0200 Subject: fix typo --- Sources/bar/bar.docc/patches.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'Sources') diff --git a/Sources/bar/bar.docc/patches.md b/Sources/bar/bar.docc/patches.md index e2646f3..de0514a 100644 --- a/Sources/bar/bar.docc/patches.md +++ b/Sources/bar/bar.docc/patches.md @@ -18,7 +18,7 @@ The file contains a diff of the changes needed to add a specific feature. For example, to apply a patch from the *bar* collection: ```shell -curl -sL https://raw.githubusercontent.com/paninihouse/bar/refs/heads/master/patches/bar-font_offset-20260810-11d813c.patch | patch -p1 +curl -sL https://raw.githubusercontent.com/paninihouse/bar/refs/heads/master/patches/patch-font_offset-20260810-11d813c.patch | patch -p1 ``` After applying the patch, rebuild the program: @@ -63,13 +63,13 @@ This modular approach lets the community mix and match features without duplicat When publishing a patch, use a descriptive file name that follows the convention: ``` -bar---.patch +patch---.patch ``` For example: ``` -bar-font_offset-20260810-11d813c.patch +patch-font_offset-20260810-11d813c.patch ``` The date pinpoints which version of the code the patch was made against, and the commit hash makes it easy to look up the exact state of the repository at that point. -- cgit v1.2.3