verbose fetches not overly verbose

[Stefan Beller <sbeller@google.com>]

        $ git clone https://github.com/gitster/git tmpgit2 -v -v -v
        Cloning into 'tmpgit2'...
        Server supports multi_ack_detailed
        Server supports no-done
        Server supports side-band-64k
        Server supports ofs-delta
        Server version is git/2:2.6.5~dgit-checksum-v5-1484-gfc2423c
        want 867ad08a2610526edb5723804723d371136fc643 (refs/heads/ab/hooks)
        want 4a6ada32cb64b0eba8b6f995e4230f0c722fd580
(refs/heads/ad/bisect-cleanup)
        want 06e6a745064c4f2f827177f6d92f4b9adb018200
(refs/heads/ad/bisect-terms)
        ...
        [a lot more wants, cut]
        want 47e8b7c56a5504d463ee624f6ffeeef1b6d007c1 (refs/tags/v2.9.1)
        done
        POST git-upload-pack (gzip 63203 to 31673 bytes)
        remote: Counting objects: 201614, done.
        remote: Total 201614 (delta 0), reused 0 (delta 0), pack-reused 201614
        Receiving objects: 100% (201614/201614), 88.76 MiB | 32.86 MiB/s, done.
        Resolving deltas: 100% (147442/147442), done.
        Checking connectivity... done.

Now the same for fetch:

        $ cd tmpgit2
        $ git fetch -v -v -v
        From https://github.com/gitster/git
         = [up to date]      master     -> origin/master
         = [up to date]      ab/hooks   -> origin/ab/hooks
         = [up to date]      ad/bisect-cleanup -> origin/ad/bisect-cleanup
         = [up to date]      ad/bisect-terms -> origin/ad/bisect-terms
        ...
         [a lot more wants, cut]

It is missing the want lines completely. I guess that is not that intentional,
but rather we forgot to add the verbosity option correctly to the
fetch in the transport layer.
Looking at the transport code, I am confused on both how the wants are
printed in the clone
case as well as how they are not printed in the fetch case.

Any hints?

(I could use GIT_TRACE_PACKET as a work around, but it's just a hack.)

Thanks,
Stefan