GNU bug report logs - #65130
Request for merging "elogind-updates" branch

Previous Next

Full log

Message #14 received at 65130 <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: 宋文武 <iyzsong <at> envs.net>
Cc: 65130 <at> debbugs.gnu.org, Efraim Flashner <efraim <at> flashner.co.il>
Subject: Re: bug#65130: Request for merging "elogind-updates" branch
Date: Sun, 13 Aug 2023 11:04:01 -0400

Hi,

宋文武 <iyzsong <at> envs.net> writes:

> Maxim Cournoyer <maxim.cournoyer <at> gmail.com> writes:
>
>> Hi,
>>
>> I think this branch is ready to go.  I've tested a Guix System using it
>> on a x200 and it behaves correctly.
>
> Hello, we currently have 3 request for merging (rust-team,
> elogind-updates, kde-updates) now, should we do the merge in order by:
>
> 1. merge master into rust-team (if needed), wait it build, merge
>    rust-team into master.
> 2. merge master into elogind-updates, then wait it build on CI, merge
>    elogind-updates into master.
> 3. merge master into kde-updates, then wait it build on CI, merge
>    kde-updates into master.
>    
> Or merge both rust-team, elogind-updates and master into kde-updates,
> and merge it once into master?  Give changes in those 3 are isolated but
> require rebuilding a lot, I think to merge them into master once can
> save a little work for us and CI.

Since rust-team is already mostly built at this point, I'd merge it
as-is.

I think we should keep the branch separated to preserve as much insights
into new failures as we can from the QA tooling.

-- 
Thanks,
Maxim

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.