osama/slock
1
0
Fork 0
mirror of https://github.com/mintycube/slock.git synced 2024-10-18 05:05:52 +02:00
Code Issues Packages Projects Releases Wiki Activity

Bump to 4f04554.

Browse Source 
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
This commit is contained in:
bakkeby 2022-10-06 15:29:45 +02:00
parent 3131706fc5
commit 780a7887a3
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Makefile
View File

@ -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}

4
README.md
View File

@ -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.