diff options
| author | Tharre <tharre3@gmail.com> | 2014-08-14 18:28:19 +0200 |
|---|---|---|
| committer | Tharre <tharre3@gmail.com> | 2014-08-14 18:28:19 +0200 |
| commit | e7a1310f6f0c1545ce0e836cc67fed904a635506 (patch) | |
| tree | 3a032b6cfa11231ce391197bf509a24ba395e64e /README.md | |
| parent | 5a4cecf4f020de36df1ef4de81dc1b87987535cd (diff) | |
| download | redo-e7a1310f6f0c1545ce0e836cc67fed904a635506.tar.gz redo-e7a1310f6f0c1545ce0e836cc67fed904a635506.tar.xz redo-e7a1310f6f0c1545ce0e836cc67fed904a635506.zip | |
Update README.md, format it to obey the 80 character rule
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 15 |
1 files changed, 11 insertions, 4 deletions
@@ -1,10 +1,17 @@ # What is redo? -`redo` provides an elegant and minimalistic way of rebuilding files from source. The design stems from Daniel J. Bernstein, who published a basic concept about how `redo` should work on his [website](http://cr.yp.to/redo.html). +`redo` provides an elegant and minimalistic way of rebuilding files from source. +The design stems from Daniel J. Bernstein, who published a basic concept about +how `redo` should work on his [website](http://cr.yp.to/redo.html). -If you want more detailed information about `redo`, a working python implementation of `redo` already exists [here](https://github.com/apenwarr/redo). +If you want more detailed information about `redo`, a working python +implementation already exists [here](https://github.com/apenwarr/redo). # About this implementation -The goal of this project is not only to implement `redo` in C, but also to rethink and improve it. This also means that this project will not try be compatible with other implementations of `redo`, although this shouldn't prove problematic. +The goal of this project is not only to implement `redo` in C, but also to +rethink and improve it. As a consequence, this project will _not_ be compatible +with other implementations of `redo`. # Project status [](https://travis-ci.org/Tharre/redo) -This is work in progress, many features are still missing and the behaviour is not set in stone yet. Missing features include parallel builds, recursive checking for do-files, automatic cleanup of build files and probably a lot more. +This is work in progress, many features are still missing and the behaviour is +not set in stone yet. Missing features include parallel builds, recursive +checking for do-files, automatic cleanup of built files and probably a lot more. |