A default run of patches-to-git may not output anything. We should change this to make the tool output progress information, like git, and thus provide the developer with an assurance that things ran as they should.

The verbose (-v) output is great, but too verbose.

I would suggest something like:
Copying patches to glibc-patches... 0%
Copying patches to glibc-patches... 50%
Copying patches to glibc-patches... 100%
Copying patches to glibc-patches... Done.

The other way around:
Copying commits from glibc-patches... 0%
...
Copying commits from glibc-patches... Done.

In my mind the operation modes would look like this:
(1) No special options, some output to stdout so developer knows that the process completed successfully.
(2) Verbose output mode using -v, so developer can review exactly which patches or commits were processed.
(3) Quiet mode (absolutely no output) using -q, so developer can run automated.

This bug is about (1). I have filed another bug for (3).