On Tue, Jun 22, 2010 at 12:35:32PM -0600, Eric Blake wrote: > On 06/22/2010 12:24 PM, Hugh O. Brock wrote: > >> Correct, we shouldn't change this behaviour - it'll break apps parsing > >> the output > > > > FWIW Rich Jones complains that the output as it stands is nigh on > > unparseable anyway. Perhaps we should consider that a bug, and fix > > it... > > The new --details option is our chance to change output - it outputs > whatever format we want, because it is a new flag; Rich, do you have any > preferences about what it _should_ output? --details is still targetted at humans. If you want something more easily parseable it should use a structured format like CSV. So I don't think we should be overloading --details for this purpose. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list