On 04/09/15 13:47, Ján Tomko wrote:
> On Fri, Sep 04, 2015 at 01:10:02PM +0200, Erik Skultety wrote:
>> When looking at commit 4fdd873f, I've come to notice, that after my changes
>> to
>> virsh (834c5720), vshInit always calls vshReadlineInit and that is because
>> client mode defaults to
When looking at commit 4fdd873f, I've come to notice, that after my changes to
virsh (834c5720), vshInit always calls vshReadlineInit and that is because
client mode defaults to interactive which might be changed after command line
arguments are parsed. So this series addresses this minor issue
On Fri, Sep 04, 2015 at 01:10:02PM +0200, Erik Skultety wrote:
> When looking at commit 4fdd873f, I've come to notice, that after my changes to
> virsh (834c5720), vshInit always calls vshReadlineInit and that is because
> client mode defaults to interactive which might be changed after command
