all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: merging r-team branch
Date: Sun, 7 Jul 2024 20:04:41 +0300	[thread overview]
Message-ID: <ZorKqRb9W89_dzM4@pbp> (raw)
In-Reply-To: <87v81hslzs.fsf@elephly.net>

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

On Sun, Jul 07, 2024 at 09:24:23AM +0200, Ricardo Wurmus wrote:
> Hi Guix,
> 
> the r-team branch has been built successfully.  It contains updates to R
> and both CRAN and Bioconductor packages.
> 
> It is the last in the queue of branches to be merged:
> 
>     core-updates #70456
>     tex-team     #70915
>     python-team  #71408
>     kde-team     #71614
>     rust-team    #71703
>     r-team       #71901
> 
> It touches very few packages that are not related to R.  The exception
> is apache-arrow.
> 
> I know that while the python-team branch is farther up the queue it is
> not actually ready to be merged, pushing up kde-team, rust-team, and
> r-team.  What is the status of the other branches in the queue?

The rust-team has no objections to you merging first.

-- 
Efraim Flashner   <efraim@flashner.co.il>   רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

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

      parent reply	other threads:[~2024-07-07 20:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-07  7:24 merging r-team branch Ricardo Wurmus
2024-07-07  7:49 ` Zheng Junjie
2024-07-15 12:53   ` Z572
2024-07-15 12:53     ` Z572
2024-07-07  8:53 ` Nicolas Goaziou via Development of GNU Guix and the GNU System distribution.
2024-07-07  9:36 ` Andreas Enge
2024-07-07 17:04 ` Efraim Flashner [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZorKqRb9W89_dzM4@pbp \
    --to=efraim@flashner.co.il \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.