Re: [PATCH v2] MAINTAINERS: Merge the Gitlab-CI section into the generic CI section

2021-03-10 Thread Fam Zheng
My time on QEMU is rather limited and I could hardly look at testing patches for long. So it makes sense to drop me. Acked-by: Fam Zheng Thanks! Fam On Mon, 8 Mar 2021 at 15:50, Thomas Huth wrote: > The status of the gitlab-CI files is currently somewhat confusing, and > it is often not quite

Re: [PATCH v2] MAINTAINERS: Merge the Gitlab-CI section into the generic CI section

2021-03-09 Thread Alex Bennée
Thomas Huth writes: > The status of the gitlab-CI files is currently somewhat confusing, and > it is often not quite clear whether a patch should go via my tree or > via the testing tree of Alex. That situation has grown historically... > Initially, I was the only one using the gitlab-CI, just

Re: [PATCH v2] MAINTAINERS: Merge the Gitlab-CI section into the generic CI section

2021-03-08 Thread Philippe Mathieu-Daudé
On 3/8/21 6:49 PM, Willian Rampazzo wrote: > On Mon, Mar 8, 2021 at 12:46 PM Thomas Huth wrote: >> >> The status of the gitlab-CI files is currently somewhat confusing, and >> it is often not quite clear whether a patch should go via my tree or >> via the testing tree of Alex. That situation has g

Re: [PATCH v2] MAINTAINERS: Merge the Gitlab-CI section into the generic CI section

2021-03-08 Thread Philippe Mathieu-Daudé
On 3/8/21 6:01 PM, Thomas Huth wrote: > On 08/03/2021 17.35, Philippe Mathieu-Daudé wrote: >> On 3/8/21 4:46 PM, Thomas Huth wrote: >>> The status of the gitlab-CI files is currently somewhat confusing, and >>> it is often not quite clear whether a patch should go via my tree or >>> via the testing

Re: [PATCH v2] MAINTAINERS: Merge the Gitlab-CI section into the generic CI section

2021-03-08 Thread Willian Rampazzo
On Mon, Mar 8, 2021 at 12:46 PM Thomas Huth wrote: > > The status of the gitlab-CI files is currently somewhat confusing, and > it is often not quite clear whether a patch should go via my tree or > via the testing tree of Alex. That situation has grown historically... > Initially, I was the only

Re: [PATCH v2] MAINTAINERS: Merge the Gitlab-CI section into the generic CI section

2021-03-08 Thread Wainer dos Santos Moschetta
On 3/8/21 12:46 PM, Thomas Huth wrote: The status of the gitlab-CI files is currently somewhat confusing, and it is often not quite clear whether a patch should go via my tree or via the testing tree of Alex. That situation has grown historically... Initially, I was the only one using the gitla

Re: [PATCH v2] MAINTAINERS: Merge the Gitlab-CI section into the generic CI section

2021-03-08 Thread Thomas Huth
On 08/03/2021 17.35, Philippe Mathieu-Daudé wrote: On 3/8/21 4:46 PM, Thomas Huth wrote: The status of the gitlab-CI files is currently somewhat confusing, and it is often not quite clear whether a patch should go via my tree or via the testing tree of Alex. That situation has grown historically

Re: [PATCH v2] MAINTAINERS: Merge the Gitlab-CI section into the generic CI section

2021-03-08 Thread Philippe Mathieu-Daudé
On 3/8/21 4:46 PM, Thomas Huth wrote: > The status of the gitlab-CI files is currently somewhat confusing, and > it is often not quite clear whether a patch should go via my tree or > via the testing tree of Alex. That situation has grown historically... > Initially, I was the only one using the gi

[PATCH v2] MAINTAINERS: Merge the Gitlab-CI section into the generic CI section

2021-03-08 Thread Thomas Huth
The status of the gitlab-CI files is currently somewhat confusing, and it is often not quite clear whether a patch should go via my tree or via the testing tree of Alex. That situation has grown historically... Initially, I was the only one using the gitlab-CI, just for my private repository there.