From: Ricardo Wurmus <rekado@elephly.net>
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org
Subject: Re: branch master updated (2bea3f2562 -> 6745d692d4)
Date: Thu, 09 May 2024 22:34:57 +0200 [thread overview]
Message-ID: <87fruqrafi.fsf@elephly.net> (raw)
In-Reply-To: <875xvnfi17.fsf@cbaines.net> (Christopher Baines's message of "Thu, 09 May 2024 10:31:32 +0100")
Hi,
> guix-commits@gnu.org writes:
>
>> rekado pushed a change to branch master
>> in repository guix.
>>
>> from 2bea3f2562 gnu: kubo: Unbundle go-cidutil, go-log and go-ipfs-util.
>> new 79c2b32337 gnu: r-with-tests: Update to 4.4.0.
>
> ...
>
>> new 5ad635ec49 gnu: r-job: Update to 0.3.1.
>> new 6f95883d01 FIXUP r-infercnv
>> new 1b6f915a88 gnu: r-rcppspdlog: Update to 0.0.17.
>
> ...
>
>> new babafe251c gnu: r-icellnet: Update to 2.2.1-1.e10ee4a.
>> new ba8d10c65a FIXUP r-bigmelon
>> new 6745d692d4 gnu: rcas-web: Update to latest commit.
>>
>> The 670 revisions listed above as "new" are entirely new to this
>> repository and will be described in separate emails. The revisions
>> listed as "add" were already present in the repository and have only
>> been added to this reference.
>
> Were these changes meant to be pushed to master?
Yes, they had been built on ci.guix.gnu.org in the r-updates jobset.
> These changes from r-updates have effectively jumped the queue past
> those on the core-updates and gnome-team branches, and since there was
> never a "Request for merging" issue opened [1], the bordeaux build farm
> is going to be delayed in building gnome-team as it tries to catch up
> with master.
>
> 1: https://guix.gnu.org/manual/devel/en/html_node/Managing-Patches-and-Branches.html
Oh, this is new to me. I've just read it. (Good to know also for the
upcoming merge of the python-team branch!)
My apologies for not following this process for r-updates. I'm hearing
about this for the first time now. (I hope the previous wip-python-team
didn't cause too many problems for bordeaux.)
> Also, there appears to be a couple of FIXUP commits that were pushed.
Yeah, it's very annoying that I missed these two FIXUP commits :-/
--
Ricardo
next prev parent reply other threads:[~2024-05-09 20:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <171516621153.22775.5117245167398918147@vcs2.savannah.gnu.org>
2024-05-09 9:31 ` branch master updated (2bea3f2562 -> 6745d692d4) Christopher Baines
2024-05-09 20:34 ` Ricardo Wurmus [this message]
2024-05-10 11:58 ` Christopher Baines
2024-05-10 12:36 ` Ricardo Wurmus
2024-05-10 16:57 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-05-10 21:00 ` Attila Lendvai
2024-05-10 15:28 ` kiasoc5
2024-05-10 16:53 ` Tomas Volf
2024-05-10 20:46 ` Ricardo Wurmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fruqrafi.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=mail@cbaines.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).