Re: [libvirt] [PATCH] testutils: Explicitly name virTestCompare*() arguments

2019-02-22 Thread Andrea Bolognani
On Wed, 2019-02-20 at 07:33 -0500, John Ferlan wrote: > On 2/20/19 2:37 AM, Michal Privoznik wrote: > > On 2/19/19 9:19 PM, John Ferlan wrote: > > > Assuming extraction (sigh) of the VIR_AUTOFREE, > > > > While I'd definitely want this to be split into two patches if it was > > fixing something

Re: [libvirt] [PATCH] testutils: Explicitly name virTestCompare*() arguments

2019-02-22 Thread Michal Privoznik
On 2/20/19 1:56 PM, Andrea Bolognani wrote: On Wed, 2019-02-20 at 07:33 -0500, John Ferlan wrote: On 2/20/19 2:37 AM, Michal Privoznik wrote: On 2/19/19 9:19 PM, John Ferlan wrote: Assuming extraction (sigh) of the VIR_AUTOFREE, While I'd definitely want this to be split into two patches if

Re: [libvirt] [PATCH] testutils: Explicitly name virTestCompare*() arguments

2019-02-22 Thread Michal Privoznik
On 2/19/19 9:19 PM, John Ferlan wrote: Assuming extraction (sigh) of the VIR_AUTOFREE, Reviewed-by: John Ferlan While I'd definitely want this to be split into two patches if it was fixing something under src/, but this is under tests/ and therefore I did not bother. The reason for

Re: [libvirt] [PATCH] testutils: Explicitly name virTestCompare*() arguments

2019-02-20 Thread Andrea Bolognani
On Wed, 2019-02-20 at 14:06 +0100, Michal Privoznik wrote: > On 2/20/19 1:56 PM, Andrea Bolognani wrote: > > There is barely ever a reason *not* to split changes into smaller, > > independent units; having to write "at the same time" in the commit > > message should be your hint that you're doing

Re: [libvirt] [PATCH] testutils: Explicitly name virTestCompare*() arguments

2019-02-20 Thread John Ferlan
On 2/20/19 2:37 AM, Michal Privoznik wrote: > On 2/19/19 9:19 PM, John Ferlan wrote: >> Assuming extraction (sigh) of the VIR_AUTOFREE, >> >> Reviewed-by: John Ferlan >> > > While I'd definitely want this to be split into two patches if it was > fixing something under src/, but this is under

Re: [libvirt] [PATCH] testutils: Explicitly name virTestCompare*() arguments

2019-02-19 Thread John Ferlan
On 2/19/19 12:22 PM, Michal Privoznik wrote: > Currently, some arguments are called strcontent and strsrc, or > content and src or some other combination. This makes it > impossible to see at the first glance what argument is supposed > to represent 'expected' value and which one represents

[libvirt] [PATCH] testutils: Explicitly name virTestCompare*() arguments

2019-02-19 Thread Michal Privoznik
Currently, some arguments are called strcontent and strsrc, or content and src or some other combination. This makes it impossible to see at the first glance what argument is supposed to represent 'expected' value and which one represents 'actual' value. Rename the arguments to make it obvious.