On 12/03/24 3:08 am, Peter Xu wrote:
On Tue, Mar 12, 2024 at 03:01:51AM +0530, Het Gala wrote:
On 12/03/24 2:55 am, Peter Xu wrote:
On Sat, Mar 09, 2024 at 01:11:45PM +0530, Het Gala wrote:
Can find the reference to the githab pipeline (before patchset) :
https://urldefense.proofpoint.com/v2/url?u=https-3A__gitlab.com_galahet_Qemu_-2D_pipelines_1207185095&d=DwIBaQ&c=s883GpUCOChKOHiocYtGcg&r=-qwZZzrw4EKSsq0BK7MBd3wW1WEpXmJeng3ZUT5uBCg&m=y2xUaOwvRVC5eTpFNEdxb37JYDdxN61W406HlCyx3CWIVyBRgLwjJhAYALZLinoi&s=vZRNX33_DuLO1TsfTpYR_s9bf_EMFm3oHHH_eg57zE0&e=
Can find the reference to the githab pipeline (after patchset) :
https://urldefense.proofpoint.com/v2/url?u=https-3A__gitlab.com_galahet_Qemu_-2D_pipelines_1207183673&d=DwIBaQ&c=s883GpUCOChKOHiocYtGcg&r=-qwZZzrw4EKSsq0BK7MBd3wW1WEpXmJeng3ZUT5uBCg&m=y2xUaOwvRVC5eTpFNEdxb37JYDdxN61W406HlCyx3CWIVyBRgLwjJhAYALZLinoi&s=C73ka3k3ouAuRJYNVLPIBQiWx3jDFDDvVYDiEYqfE04&e=
Het,
Please still copy me for any migration patches. In this case Fabiano is
looking it'll be all fine, but it will still help me on marking the emails.
Thanks,
So sorry about that Peter. I am aware that you and Fabiano are the go to
migration
maintainers. I thought I emailed or cc'd all the stakeholders that should be
involved
for this patchset series. Even in earlier series of this patchset, you were
cc'ed,
but somehow I just forgot to cc you for this patchset. Sure, will take care
from next
time. Again apologies for the mixup :)
No problem at all. As long as you have at least 1 maintainers copied,
logically nothing will get lost. It's just that it helps me in the routines.
Are you managing cc list manually for each version? In that case I suggest
you have a look at Stefan's tool:
I used to earlier. But lately markus introduced me to
scripts/get_maintainers.pl -f <file>
It gives list of all the maintainers handling that particular file.
So that helped me for this patchset.
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_stefanha_git-2Dpublish&d=DwIBaQ&c=s883GpUCOChKOHiocYtGcg&r=-qwZZzrw4EKSsq0BK7MBd3wW1WEpXmJeng3ZUT5uBCg&m=ydJfb02Wuk_NnlYl8-RkRkYXzWNpzlEht7yj5kakeAlz_WPoD6yvC7b-fVCeLzom&s=8KSe9MiMzmHda3uZ_uaGCIEjub4tSzpeDTpZZwq5knc&e=
Thanks a lot Peter, looks cool. Will try to explore and use git-publish
and its different methods for next patchset.
It might help a great deal in patch managements at least to me, and it
definitely covers more than maintaining the cc list for a patchset.
Yes, it looks like there are a lot of useful methods that I can leverage
in future :)
Regards,
Het Gala
