Eric Blake
50f7960d37
virsh: kill over-engineered asprintf failure recovery ...
I noticed this while shortening switch statements via VIR_ENUM.
Basically, the only ways virAsprintf can fail are if we pass a
bogus format string (but we're not THAT bad) or if we run out
of memory (but it already warns on our behalf in that case).
Throw away the cruft that tries too hard to diagnose a printf
failure.
* tools/virsh-volume.c (cmdVolList): Simplify.
* tools/virsh-pool.c (cmdPoolList): Likewise.
Signed-off-by: Eric Blake <eblake@redhat.com>
2014-02-24 11:47:18 -07:00
2014-02-04 10:57:21 +01:00
2012-12-11 19:54:37 -05:00
2014-01-09 09:32:55 +01:00
2014-02-24 10:54:37 +01:00
2012-03-05 13:18:24 +01:00
2014-01-21 13:19:46 +02:00
2013-09-03 14:06:11 +02:00
2013-09-03 14:06:11 +02:00
2014-02-24 11:47:18 -07:00
2012-09-20 16:30:55 -06:00
2014-02-24 11:47:18 -07:00
2012-09-20 16:30:55 -06:00
2013-06-25 15:37:20 +02:00
2014-02-06 14:09:15 +01:00
2012-09-20 16:30:55 -06:00
2013-11-13 10:07:32 +01:00
2012-09-20 16:30:55 -06:00
2014-02-24 11:47:18 -07:00
2012-09-20 16:30:55 -06:00
2013-10-15 06:47:24 -06:00
2012-09-20 16:30:55 -06:00
2013-11-13 10:07:32 +01:00
2012-09-20 16:30:55 -06:00
2014-02-24 11:47:18 -07:00
2012-09-20 16:30:55 -06:00
2013-11-13 10:07:32 +01:00
2012-09-20 16:30:55 -06:00
2013-08-20 17:53:49 +02:00
2012-09-20 16:30:55 -06:00
2014-02-24 11:47:18 -07:00
2012-09-20 16:30:55 -06:00
2014-02-20 16:23:27 -07:00
2014-02-20 16:23:27 -07:00
2014-02-20 16:23:27 -07:00
2013-07-10 11:07:31 +02:00
2012-09-20 16:30:55 -06:00
2012-09-20 16:30:55 -06:00
2012-09-20 16:30:55 -06:00
2012-09-20 16:30:55 -06:00
2012-09-20 16:30:55 -06:00
2012-09-20 16:30:55 -06:00
2014-01-20 14:35:08 +01:00
2013-08-08 16:36:31 +01:00
2013-09-06 11:05:56 +08:00
2013-08-19 20:25:53 -06:00
2013-08-28 13:50:10 +02:00
2013-09-13 14:57:52 +02:00
50f7960d37