diff options
| author | bakkeby <[email protected]> | 2020-07-08 20:00:25 +0200 |
|---|---|---|
| committer | bakkeby <[email protected]> | 2020-07-08 20:00:25 +0200 |
| commit | 474c91ea0c300f785821598a7c8e3252708cacbd (patch) | |
| tree | b7c2288a5adac34e5177c890bedbe2f844713cd8 /README.md | |
| parent | fbaa215a1472d1bc627ec24588b4fba9f7d0b130 (diff) | |
| download | dwm-flexipatch-474c91ea0c300f785821598a7c8e3252708cacbd.tar.gz dwm-flexipatch-474c91ea0c300f785821598a7c8e3252708cacbd.zip | |
dwm.1: fix wrong text in man page (aaad5f)
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -1,4 +1,4 @@ -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. +This dwm 6.2 (aaad5f, 2020-07-08) 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 |
