all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: jgart <jgart@dismail.de>, 54584@debbugs.gnu.org
Cc: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: [bug#54584] [PATCH v2] gnu: python-slixmpp: Update to 1.8.1.
Date: Sat, 16 Apr 2022 17:25:05 +0200	[thread overview]
Message-ID: <fe3f1ab95fb1bbb2a6e2bed73df653c822d97948.camel@telenet.be> (raw)
In-Reply-To: <20220416142609.11144-1-jgart@dismail.de>

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

jgart via Guix-patches via schreef op za 16-04-2022 om 10:26 [-0400]:
> * gnu/packages/python-xyz.scm (python-slixmpp): Update to 1.8.1.
> [arguments]: Remove trailing boolean, use new style, and use 
> cc-for-target.
> [native-inputs]: Use new style.
> 
> Hi Maxim,
> 
> Here is the second version of this patch.
> 
> I think this adds what you suggested in the code review.

I haven't looked at the upstream 1.5.2->1.8.1 diff, but the CC->cc-for-
target and delabelisation LGTM.

Greetings,
Maxime.

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

  reply	other threads:[~2022-04-16 15:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-26 18:27 [bug#54584] [PATCH] gnu: python-slixmpp: Update to 1.8.1 jgart via Guix-patches via
2022-03-26 21:16 ` Maxime Devos
2022-04-16 14:26 ` [bug#54584] [PATCH v2] " jgart via Guix-patches via
2022-04-16 15:25   ` Maxime Devos [this message]
2022-04-24  3:32   ` Maxim Cournoyer
2022-04-24  6:15     ` jgart via Guix-patches via
2022-05-22  5:08       ` [bug#54584] [PATCH] " Maxim Cournoyer
2022-05-22 19:35         ` jgart via Guix-patches via
2023-09-01 23:41 ` bug#54584: " Vagrant Cascadian

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=fe3f1ab95fb1bbb2a6e2bed73df653c822d97948.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=54584@debbugs.gnu.org \
    --cc=jgart@dismail.de \
    --cc=maxim.cournoyer@gmail.com \
    /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.