1 files changed, 2 insertions(+), 2 deletions(-)

M README.md

@@ 1,4 1,4 @@
-Similar to [dwm-flexipatch](https://github.com/bakkeby/dwm-flexipatch) this slock 1.4 project has a different take on 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 slock 1.4 (701aa9, 2017-03-25) project has a different take on 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 `capscolor` patch then you would only need to flip this setting from 0 to 1 in [patches.h](https://github.com/bakkeby/slock-flexipatch/blob/master/patches.h):
 ```c


@@ 56,4 56,4 @@ Refer to [https://tools.suckless.org/slock/](https://tools.suckless.org/slock/) 
       - that is, the screen is not affected by slock, but users will not be able to interact with the X session unless they enter the correct password
 
    - [xresources](https://tools.suckless.org/slock/patches/xresources/)
-      - this patch adds the ability to get colors via Xresources>
\ No newline at end of file
+      - this patch adds the ability to get colors via Xresources