all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: 53865@debbugs.gnu.org
Cc: 53865-done@debbugs.gnu.org, jgart@dismail.de
Subject: [bug#53865] [PATCH] gnu: ruby-parser: Update to 3.1.0.0.
Date: Wed, 09 Feb 2022 21:00:36 +0100	[thread overview]
Message-ID: <87o83fvmhn.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <20220209130213.GB5766@gac.attlocal.net> (jgart via Guix-patches via's message of "Wed, 9 Feb 2022 13:02:13 -0500")

jgart via Guix-patches via <guix-patches@gnu.org> writes:

> On Wed, 09 Feb 2022 16:05:52 +0100 Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
>> Hello,
>> 
>> jgart via Guix-patches via <guix-patches@gnu.org> writes:
>> 
>> > * gnu/packages/ruby.scm (ruby-parser): Update to 3.1.0.0.
>> 
>> Applied on core-updates (it entails building 5k packages).
>
> Thanks Nicolas!
>
> What is your workflow for determining whether it goes to core-updates?

I did

  guix refresh --list-dependent ruby

It reported 5000+ packages. According to Submitting Patches section of
the manual, above 1800, it should go to core-updates (at the moment).

HTH,
-- 
Nicolas Goaziou




  reply	other threads:[~2022-02-09 20:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08  2:08 [bug#53865] [PATCH] gnu: ruby-parser: Update to 3.1.0.0 jgart via Guix-patches via
2022-02-09 15:05 ` bug#53865: " Nicolas Goaziou
2022-02-09 18:02   ` [bug#53865] " jgart via Guix-patches via
2022-02-09 20:00     ` Nicolas Goaziou [this message]
2022-02-09 21:05       ` jgart via Guix-patches via
2022-02-09 21:16         ` jgart via Guix-patches via
2022-02-09 21:24           ` Nicolas Goaziou
2022-02-09 22:10             ` jgart via Guix-patches via

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=87o83fvmhn.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=53865-done@debbugs.gnu.org \
    --cc=53865@debbugs.gnu.org \
    --cc=jgart@dismail.de \
    /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.