> On 19 May 2023, at 08:25, Michal Orzel wrote:
>
>
> On 19/05/2023 09:12, Luca Fancellu wrote:
>>
>>
>>> On 19 May 2023, at 08:08, Michal Orzel wrote:
>>>
>>> Hi Luca,
>>>
>>> On 17/05/2023 02:44, Stefano Stabellini wrote:
On Thu, 4 May 2023, Luca Fancellu wrote:
> r
On 19/05/2023 09:12, Luca Fancellu wrote:
>
>
>> On 19 May 2023, at 08:08, Michal Orzel wrote:
>>
>> Hi Luca,
>>
>> On 17/05/2023 02:44, Stefano Stabellini wrote:
>>>
>>>
>>> On Thu, 4 May 2023, Luca Fancellu wrote:
repository in the reports
Currently the cppcheck report entries
> On 19 May 2023, at 08:08, Michal Orzel wrote:
>
> Hi Luca,
>
> On 17/05/2023 02:44, Stefano Stabellini wrote:
>>
>>
>> On Thu, 4 May 2023, Luca Fancellu wrote:
>>> repository in the reports
>>>
>>> Currently the cppcheck report entries shows the relative file path
>>> from the /xen folder
Hi Luca,
On 17/05/2023 02:44, Stefano Stabellini wrote:
>
>
> On Thu, 4 May 2023, Luca Fancellu wrote:
>> repository in the reports
>>
>> Currently the cppcheck report entries shows the relative file path
>> from the /xen folder of the repository instead of the base folder.
>> In order to ease t
On Thu, 4 May 2023, Luca Fancellu wrote:
> repository in the reports
>
> Currently the cppcheck report entries shows the relative file path
> from the /xen folder of the repository instead of the base folder.
> In order to ease the checks, for example, when looking a git diff
> output and the repo
repository in the reports
Currently the cppcheck report entries shows the relative file path
from the /xen folder of the repository instead of the base folder.
In order to ease the checks, for example, when looking a git diff
output and the report, use the repository folder as base.
Signed-off-by
