GNU bug report logs - #77309
[PATCH] gnu: ruby-3.3: Upgrade to 3.3.7

Previous Next

Full log

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

From: Christopher Baines <mail <at> cbaines.net>
To: Andreas Enge <andreas <at> enge.fr>
Cc: guix <at> cbaines.net, 77309 <at> debbugs.gnu.org, ngraves <at> ngraves.fr,
 Remco van 't Veer <remco <at> remworks.net>, sharlatanus <at> gmail.com
Subject: Re: [PATCH] gnu: ruby-3.3: Upgrade to 3.3.7
Date: Wed, 14 May 2025 11:38:09 +0100

[Message part 1 (text/plain, inline)]

Andreas Enge <andreas <at> enge.fr> writes:

> This is already part of the ruby-team branch, which I am cc-ing along
> with people who have worked on this branch.

I think this is a good example of point 2 for managing branches on [1]:

   Any changes that can be made on the master branch, should be made on
   the master branch. If a commit can be split to apply part of the
   changes on master, this is good to do.

1: https://guix.gnu.org/manual/devel/en/html_node/Managing-Patches-and-Branches.html


Looking at the number of packages affected from QA, this change can go
straight to master, so shouldn't go via a branch.

[signature.asc (application/pgp-signature, inline)]

Previous Next

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