commit fdae39e8b8e37d73305f37afd97a566d28a57ee0
parent dba3d178a444249532832f3141966170fd66d88e
Author: Bakkeby <bakkeby@gmail.com>
Date: Wed, 20 Mar 2024 08:04:33 +0100
bump version to 0.9.1
ref.
https://git.suckless.org/st/commit/5ce971628106fb767ef91bf4386227423f5fdf98.html
Diffstat:
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/README.md b/README.md
@@ -1,4 +1,4 @@
-Similar to [dwm-flexipatch](https://github.com/bakkeby/dwm-flexipatch) this st 0.9 (f20e169, 2024-03-17) project has a different take on st patching. It uses preprocessor directives to decide whether or not to include a patch during build time. Essentially this means that this build, for better or worse, contains both the patched _and_ the original code. The aim being that you can select which patches to include and the build will contain that code and nothing more.
+Similar to [dwm-flexipatch](https://github.com/bakkeby/dwm-flexipatch) this st 0.9.1 (5ce9716, 2024-03-19) project has a different take on st patching. It uses preprocessor directives to decide whether or not to include a patch during build time. Essentially this means that this build, for better or worse, contains both the patched _and_ the original code. The aim being that you can select which patches to include and the build will contain that code and nothing more.
For example to include the `alpha` patch then you would only need to flip this setting from 0 to 1 in [patches.h](https://github.com/bakkeby/st-flexipatch/blob/master/patches.def.h):
```c
diff --git a/config.mk b/config.mk
@@ -1,5 +1,5 @@
# st version
-VERSION = 0.9
+VERSION = 0.9.1
# Customize below to fit your system
