30.07.2023 21:03, Stefan Weil via wrote:
Signed-off-by: Stefan Weil
---
This patch was triggered by a spelling check for the generated
QEMU documentation using codespell. It does not try to fix all
typos which still exist in the QEMU code, but has a focus on
those required to fix the documentat
On 30/7/23 20:03, Stefan Weil wrote:
Signed-off-by: Stefan Weil
---
This patch was triggered by a spelling check for the generated
QEMU documentation using codespell. It does not try to fix all
typos which still exist in the QEMU code, but has a focus on
those required to fix the documentation.
On 30/7/23 20:03, Stefan Weil wrote:
Signed-off-by: Stefan Weil
---
This patch was triggered by a spelling check for the generated
QEMU documentation using codespell. It does not try to fix all
typos which still exist in the QEMU code, but has a focus on
those required to fix the documentation.
On Sun, 30 Jul 2023 at 19:55, Stefan Weil via wrote:
>
> Signed-off-by: Stefan Weil
> ---
Reviewed-by: Peter Maydell
thanks
-- PMM
Signed-off-by: Stefan Weil
---
This patch was triggered by a spelling check for the generated
QEMU documentation using codespell. It does not try to fix all
typos which still exist in the QEMU code, but has a focus on
those required to fix the documentation. Nevertheless some code
comments with t
On Sat, 29 Oct 2022 at 13:27, Stefan Weil via wrote:
>
> Most of them were found and fixed using codespell.
>
> Signed-off-by: Stefan Weil
> ---
Aside from Peter's comments:
Reviewed-by: Stefan Hajnoczi
On Sat, 29 Oct 2022 at 18:25, Stefan Weil wrote:
>
> Most of them were found and fixed using codespell.
>
> Signed-off-by: Stefan Weil
> ---
>
> My focus was fixing typos which are relevant for the generated documentation.
>
> codespell finds many more typos in source code, and adding it to the
Most of them were found and fixed using codespell.
Signed-off-by: Stefan Weil
---
My focus was fixing typos which are relevant for the generated documentation.
codespell finds many more typos in source code, and adding it to the continuous
integration checks looks more and more like a good idea
