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

2021-03-10 Thread Willian Rampazzo
On Tue, Mar 9, 2021 at 8:24 AM 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 o

Re: [PATCH v3] 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 v3] MAINTAINERS: Merge the Gitlab-CI section into the generic CI section

2021-03-09 Thread Philippe Mathieu-Daudé
On 3/9/21 12:23 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 g

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

2021-03-09 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.