unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: Lars-Dominik Braun <lars@6xq.net>
Cc: 44656@debbugs.gnu.org
Subject: [bug#44656] [PATCH] Upgrade pypy3
Date: Sun, 15 Nov 2020 19:33:02 +0000	[thread overview]
Message-ID: <87zh3ibekx.fsf@cbaines.net> (raw)
In-Reply-To: <20201115123911.GA1956@noor.fritz.box>

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


Lars-Dominik Braun <lars@6xq.net> writes:

> the first patch in this series upgrades pypy3 to 7.3.2 and the second
> adjusts several aspects of the package.

Hi,

Given that the two patches really form just one change, the version
change with the necessary other changes to the package, would it be
possible to merge most or all of the two patches together?

Effectively, anything that's essential to change about the pypy3 package
when upgrading the version would ideally be in the same commit as the
version change. One reason for this is that it makes the change easier
to understand, as the actual changes are kept together in one commit.

If there are things that aren't essential to change when changing the
version, they're fine to have in subsequent commits/patches.

Thanks,

Chris

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

  reply	other threads:[~2020-11-15 19:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-15 12:39 [bug#44656] [PATCH] Upgrade pypy3 Lars-Dominik Braun
2020-11-15 19:33 ` Christopher Baines [this message]
2020-11-15 19:55   ` Lars-Dominik Braun
2020-11-16 17:26     ` Christopher Baines
2020-11-17  9:38       ` Lars-Dominik Braun
2021-08-03 21:39 ` Maxim Cournoyer
2021-08-05 16:54   ` bug#44656: " Maxim Cournoyer
2021-08-06  7:30   ` [bug#44656] " Lars-Dominik Braun
2021-08-06 14:22     ` Maxim Cournoyer
2021-08-06 14:43       ` Lars-Dominik Braun
2021-08-07  1:29         ` Maxim Cournoyer
2021-08-07  6:59           ` Lars-Dominik Braun
2021-08-20 10:39             ` zimoun
2021-08-20 14:25               ` Lars-Dominik Braun

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=87zh3ibekx.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=44656@debbugs.gnu.org \
    --cc=lars@6xq.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).