unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Remco van 't Veer <remco@remworks.net>
Cc: 56302@debbugs.gnu.org
Subject: [bug#56302] Acknowledgement ([PATCH] gnu: ruby: Update to 2.7.6 [security fixes].)
Date: Wed, 29 Jun 2022 20:18:50 +0200	[thread overview]
Message-ID: <c2c8209c614d12b7cec0c076ba81284b5e36774b.camel@telenet.be> (raw)
In-Reply-To: <875ykjh2h9.fsf@remworks.net>

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

Remco van 't Veer schreef op wo 29-06-2022 om 18:13 [+0200]:
> 2022/06/29 18:04, Maxime Devos:
> 
> > core-updates probably won't be merged for a long time, so a graft might
> > be needed in the meantime.
> 
> So, keep this bug and make a new patch / bug for the graft?

I'd keep the 56302 to keep things orderly.  FWIW, while they can be
reviewed and applied independently, the various Ruby update patches are
all about the same thing (updating Ruby), so they could have been done
together I think (separate patches, but a single series and single
debbugs number).

TBC: to keep things orderly, let's not make a new issue with a patch
series, it's more a thing I would recommend for the future.

Greetings,
Maxime

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2022-06-29 18:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-29 15:55 [bug#56302] [PATCH] gnu: ruby: Update to 2.7.6 [security fixes] Remco van 't Veer
     [not found] ` <handler.56302.B.165651815228055.ack@debbugs.gnu.org>
2022-06-29 15:58   ` [bug#56302] Acknowledgement ([PATCH] gnu: ruby: Update to 2.7.6 [security fixes].) Remco van 't Veer
2022-06-29 16:04     ` Tobias Geerinckx-Rice via Guix-patches via
2022-06-29 16:04     ` Maxime Devos
2022-06-29 16:13       ` Remco van 't Veer
2022-06-29 18:18         ` Maxime Devos [this message]
2022-06-29 18:00 ` [bug#56302] [PATCH v2] gnu: ruby: Update to 2.7.6 [security fixes] Remco van 't Veer
2022-08-29 14:48   ` bug#56302: " Marius Bakke
2022-06-29 18:29 ` [bug#56302] [PATCH] " Maxime Devos
2022-06-29 18:57   ` Maxime Devos
2022-08-29 14:51     ` Marius Bakke

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=c2c8209c614d12b7cec0c076ba81284b5e36774b.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=56302@debbugs.gnu.org \
    --cc=remco@remworks.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).