Does editcap need to report the type of input file in verbose mode?

Summary

editcap, in verbose mode (-v for releases up to 3.6, -V after that), prints the message

File {input file} is a {type of that file} capture file.

Does this add any useful information to the output?

See https://ask.wireshark.org/question/27919/editcapexe-returns-file-mycapturefilepcapng-is-a-wireshark-pcapng-capture-file/

Steps to reproduce

Run editcap with the appropriate flag (see Summary for the appropriate flag) and an input file. (Send the standard error to the standard output, and pipe the result to a pager such as more, so the message in question doesn't get overwhelmed by Packet: {n} messages for each packet written.)

What is the current bug behavior?

The messages begin with the message in question.

What is the expected correct behavior?

The message is not printed.

Sample capture file

N/A

Relevant logs and/or screenshots

$ editcap -v  ~/captures-too-big/afscrash.pcap /tmp/output
File /Users/gharris/captures-too-big/afscrash.pcap is a AIX tcpdump - pcap capture file.
Packet: 1
Packet: 2

    ...

Build information

Editcap (Wireshark) 3.6.6 (v3.6.6-0-g7d96674e2a30)

Copyright 1998-2022 Gerald Combs <gerald@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later <https://www.gnu.org/licenses/gpl-2.0.html>
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) using Clang 11.0.0 (clang-1100.0.33.16), with GLib 2.68.4,
with zlib 1.2.11.

Running on Mac OS X 10.16, build 20G417 (Darwin 20.6.0), with Intel(R) Core(TM)
i9-9980HK CPU @ 2.40GHz (with SSE4.2), with 65536 MB of physical memory, with
GLib 2.68.4, with zlib 1.2.11, with LC_TYPE=C, binary plugins supported (0
loaded).