v1.4.0

This release adds the ‘-b/--basename’ flag.  This flag is very useful
for ensuring that you only alter the basename of the given input paths;
accidentally altering the parent paths is a common mistake.

A quick example:

    $ mkdir -p foo/bar
    $ touch foo/bar/{a,b,c}
    $ ls foo/bar/* | mmv --basename --verbose tr a-z A-Z
    renamed ‘…/foo/bar/a’ -> ‘…/foo/bar/A’
    renamed ‘…/foo/bar/b’ -> ‘…/foo/bar/B’
    renamed ‘…/foo/bar/c’ -> ‘…/foo/bar/C’

v1.3.1

This release fixes some formatting issues in the mmv(1)- and mcp(1)
manual pages.  Nothing major, but there were some visual issues in the
manuals that have been fixed.

v1.3.0

This release adds support for compiling with different binary names.
This is all being done in the hopes of getting packaged on Void Linux.

v1.2.0

This release adds the ‘mcp’ program.  ‘mcp’ works identically to ‘mmv’
except it copies files instead of moving them.  It also does not support
the ‘-n’ flag.

v1.1.0

The changes since v1.0.1 are as follows:

- Minor documentation typo fixes
- Name backup directories with timestamps, not PIDs

v1.0.1

The changes since v1.0.0 are as follows:

- When using the ‘-i’ flag, the input to the spawned process is no
  longer terminated by ‘\n’ (or ‘\0’ in the case of ‘-0’).  Any trailing
  newlines or nul-bytes are also no longer stripped.

v1.0.0

This is the initial release of mmv.  As of this release, the following
features are supported:

- Installation via a Makefile
- Documentation via a manual page
- Mapped file moves
- Backing up of data prior to any potentially-destructive actions by
  default, which can be turned off via ‘--no-backup’
- Correct handling of filenames with embedded newlines via ‘--nul’,
  ‘--encode’, and ‘--individual’.
- Testing your changes before executing them via ‘--dry-run‘.
- Getting verbose program output via ‘--verbose’.
- Pissing off suckless [1] developers by using rust.

[1]: https://suckless.org/