summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorbakkeby <[email protected]>2020-06-11 20:05:49 +0200
committerbakkeby <[email protected]>2020-06-11 20:05:49 +0200
commit7ba6ea50bfd34dbb80544000e2babf69d8457c49 (patch)
tree16466dd288db0287b5b47a9c9704bb6a1c6b05ff
parent2643894570f2ba114af9f9241d0a6c3b2cf177c8 (diff)
downloaddwm-flexipatch-7ba6ea50bfd34dbb80544000e2babf69d8457c49.tar.gz
dwm-flexipatch-7ba6ea50bfd34dbb80544000e2babf69d8457c49.zip
Upgrade to 5e34b2
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index 76cfb1f..6d0a2aa 100644
--- a/README.md
+++ b/README.md
@@ -1,4 +1,4 @@
-This dwm 6.2 (58de66, 2020-04-22) side project has a different take on dwm 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.
+This dwm 6.2 (5e34b2, 2020-06-11) side project has a different take on dwm 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/dwm-flexipatch/blob/master/patches.def.h):
```c