all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: jgart via Guix-patches via <guix-patches@gnu.org>
To: "Felix Gruber" <felgru@posteo.net>, 71984@debbugs.gnu.org
Subject: [bug#71984] [PATCH python-team] gnu: python-pygments: Update to 2.18.0.
Date: Mon, 08 Jul 2024 16:46:01 +0000	[thread overview]
Message-ID: <f345b96c813ff7090064a498628a4be599bf9048@dismail.de> (raw)
In-Reply-To: <7f411e6a-5ab0-4f56-96e6-339159c93ca0@posteo.net>

Hi Felix,

Oops my fault, I was trying to apply this on master. 🦆

Can you rebase this patch on the master branch? I can review it there. 

The python-team branch is already overloaded, stale, and requires a ton of merge conflict resolving.

Adding python-pygments to the python-team branch will only add to that 🙃

Can you also CC Sharlatan, and ask Sharlatan to try building all the dependents that this patch triggers? 

Sharlatan Hellseher <sharlatanus@gmail.com>

I won't be able to test that on my old Thinkpad X230 machine.

all the best,

jgart




  reply	other threads:[~2024-07-08 16:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-07 18:34 [bug#71984] [PATCH python-team] gnu: python-pygments: Update to 2.18.0 Felix Gruber
2024-07-08 15:18 ` jgart via Guix-patches via
2024-07-08 16:20   ` Felix Gruber
2024-07-08 16:46     ` jgart via Guix-patches via [this message]
2024-07-08 18:43       ` [bug#71984] [PATCH v2 0/2] " Felix Gruber
2024-07-08 18:43       ` [bug#71984] [PATCH v2 1/2] gnu: python-pygments: Update to 2.15.1 Felix Gruber
2024-07-18 14:56         ` Ricardo Wurmus
2024-07-08 18:43       ` [bug#71984] [PATCH v2 2/2] gnu: python-pygments: Update to 2.18.0 Felix Gruber
2024-07-08 19:42         ` 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=f345b96c813ff7090064a498628a4be599bf9048@dismail.de \
    --to=guix-patches@gnu.org \
    --cc=71984@debbugs.gnu.org \
    --cc=felgru@posteo.net \
    --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.