Log message:
Revbump all Go packages after go117 update

Log message:
Update to 1.24.0. From the changelog:

- "redo-cleanup tmp" also removes temporarily ("$3") created
  directories.

Log message:
Update to 1.23.0. From the changelog:

- "redo-ifchange"’s "-f" option forces each target rebuilding.
  Comparing to "redo", it will parallelize the process.
- Inode’s number is also stored as dependency information, just to
  prevent possible "ctime" collision of two files.
- Performance optimization: do not use target’s temporary output file
  at all, if its hash equals to already existing target’s one.  Just
  touch existing target file instead.

Log message:
Revump all Go packages after go117 update

Log message:
Update to 1.22.0. From the changelog:

- "flock" locks replaced with POSIX "fcntl" ones.  They \ 
could be more
  portable.
- "redo-depfix" command appeared, that traverses through all \ 
".redo"
  directories and their dependency files, checks if corresponding
  targets has the same content but different "ctime"/"mtime" \ 
values
  and rewrites dependencies with that updated inode information.
- With "$REDO_STOP_IF_MODIFIED=1" environment variable redo will stop
  and fail if it meet externally modified file.  By default user is
  only warned about it, but building continues for convenience.

Log message:
Revbump all Go packages after go117 update

Log message:
Add goredo, a Go implementation of djb's redo.

Originally it was just a rewrite of redo-c, but later most features of
apenwarr/redo were also implemented. Why yet another implementation? It
is featureful and has better performance comparing to shell and Python
implementation.

It passes tests from redo-sh.tests and implementation-neutral ones from
apenwarr/redo.