From 780a7887a3b976a48786f991d55fc8a474e76a25 Mon Sep 17 00:00:00 2001 From: bakkeby Date: Thu, 6 Oct 2022 15:29:45 +0200 Subject: [PATCH] Bump to 4f04554. Makefile: explicit_bzero.c was copied twice (GNU make gives a warning) bump version to 1.5 Ref. https://git.suckless.org/slock/commit/265704d73647e0d4823126bbb7ddde1d415a618d.html https://git.suckless.org/slock/commit/4f045545a25cc02c64bfc08d27ed2ccecb962292.html --- Makefile | 2 +- README.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/Makefile b/Makefile index 87dfa2b..0caaef0 100644 --- a/Makefile +++ b/Makefile @@ -40,7 +40,7 @@ dist: clean @echo creating dist tarball @mkdir -p slock-${VERSION} @cp -R LICENSE Makefile README slock.1 config.mk \ - ${SRC} explicit_bzero.c config.def.h arg.h util.h slock-${VERSION} + ${SRC} config.def.h arg.h util.h slock-${VERSION} @tar -cf slock-${VERSION}.tar slock-${VERSION} @gzip slock-${VERSION}.tar @rm -rf slock-${VERSION} diff --git a/README.md b/README.md index d4dbf47..1eeb0d9 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,5 @@ -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 +Similar to [dwm-flexipatch](https://github.com/bakkeby/dwm-flexipatch) this slock 1.5 (4f04554, +2022-10-04) 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.