Daniel P. Berrangé <berra...@redhat.com> writes: > On Tue, Apr 05, 2022 at 02:45:14PM +0200, Damien Hedde wrote: >> >> >> On 4/5/22 07:41, Markus Armbruster wrote: >> > Daniel P. Berrangé <berra...@redhat.com> writes: >> > >> > > On Wed, Mar 16, 2022 at 10:54:55AM +0100, Damien Hedde wrote: >> > > > It takes an input file containing raw qmp commands (concatenated json >> > > > dicts) and send all commands one by one to a qmp server. When one >> > > > command fails, it exits. >> > > > >> > > > As a convenience, it can also wrap the qemu process to avoid having >> > > > to start qemu in background. When wrapping qemu, the program returns >> > > > only when the qemu process terminates. >> > > > >> > > > Signed-off-by: Damien Hedde <damien.he...@greensocs.com> >> > >> > [...] >> > >> > > > I name that qmp-send as Daniel proposed, maybe qmp-test matches better >> > > > what I'm doing there ? >> > > >> > > 'qmp-test' is a use case specific name. I think it is better to >> > > name it based on functionality provided rather than anticipated >> > > use case, since use cases evolve over time, hence 'qmp-send'. >> > >> > Well, it doesn't just send, it also receives. >> > >> > qmpcat, like netcat and socat? >> > >> >> anyone against qmpcat ? > > Fine with me[1], though I would have slight preference for 'qmp-cat' > to have a common tab-completion prefix with existing qmp-shell command.
No objections to the dash.. > > With regards, > Daniel > > [1] Especially if it displays a pretty ascii art cat when you pass > the --help flag ;-P A cat "singing" to an emu? Count me in!
