Solution that is safe against adversarial input.

Use NUL bytes as delimiters, and also grep for NUL beforehand.

An example of handling multiline output from git.

This solution doesn't assume:

- That every field is a single line
- That there is only one field with spaces
- Anything else about the input format, other than it doesn't contain
  0x01 and 0x02 bytes.  (The encoding should therefore be ASCII/utf-8.)

It also has the nice property that you can change your format string
arbitrarily while not worrying about the escaping function.  I don't
want to rewrite the escaping function every time I change the format
string.  Solutions that require that are fragile.

Simplify, and add a git-specific solution.

Modify example:

- Use bash $'' because it's not specific to git.  It can be used with
  other tools too.
- 0x01 and 0x02 so as not to confuse the issue of NUL in bash strings

Inline the function for readability