unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: branch master updated (2bea3f2562 -> 6745d692d4)
Date: Fri, 10 May 2024 12:58:32 +0100	[thread overview]
Message-ID: <874jb5ev4n.fsf@cbaines.net> (raw)
In-Reply-To: <87fruqrafi.fsf@elephly.net> (Ricardo Wurmus's message of "Thu, 09 May 2024 22:34:57 +0200")

[-- Attachment #1: Type: text/plain, Size: 1003 bytes --]

Ricardo Wurmus <rekado@elephly.net> writes:

>> 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.)

Is there anything you can think of that can be done to better
communicate about process changes in the future?

This is particularly relevant at the moment since there is a patch being
discussed [2].

2: https://issues.guix.gnu.org/70549

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]

  reply	other threads:[~2024-05-10 11:59 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
2024-05-10 11:58     ` Christopher Baines [this message]
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=874jb5ev4n.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.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).