Torf

- Bugfix: --nomagnet was ignored in info mode.
- Include magnet link in output even if input is also a magnet link.
Only exclude it with --nomagnet.

- New option: --reuse <directory or torrent file> copies piece hashes from an
existing torrent file if it contains the same files. If given a directory,
it is recursively searched for a matching torrent file.
- The short flag -R for --nocreator was renamed to -A so -R can be used for
--noreuse.
- When verifying files against a torrent in previous versions, each file was
only verified up to the first corrupt piece unless --verbose was given. Now
all files are always completely verified.
- The "Files" field in --json output is now a list of objects like this:
{"Path": <relative file path>, "Size": <file size>}
- Bugfix: The --max-piece-size parameter was always used as the actual piece
size, even if it was much too large for the given content.

- New option: --threads

- Always display which tier a tracker belongs to unless the whole torrent has
only one tracker.
- New options: --include and --include-regex include files that match exclude
patterns.
- Bugfix: --exclude-regex was ignored when editing an existing torrent.

- Support for reading magnet URIs was added, e.g. "torf -i 'magnet:...' -o
foo.torrent". The missing information is downloaded from the parameters
"xs", "as", "ws" and "tr", if possible. Support for DHT and UDP trackers is
not implemented.
- The --in option now supports "-" as a parameter to read a torrent or magnet
URI from stdin.
- When verifying torrent content, a trailing slash in PATH automatically
appends the torrent's name to PATH. For example, "torf -i foo.torrent
path/to/foo" is identical to "torf -i foo.torrent path/to/" while "torf -i
foo.torrent path/to" looks for foo.torrent's files in "path/to".
- --in, --out and --name are now illegal in config files.

- Bugfix: Exclude tests from package.