From: "Ludovic Courtès" <ludo@gnu.org>
To: Sughosha <Sughosha@proton.me>
Cc: "Daniel Meißner" <daniel.meissner-i4k@ruhr-uni-bochum.de>,
"55295-done@debbugs.gnu.org" <55295-done@debbugs.gnu.org>
Subject: bug#55295: [PATCH] gnu: gcolor3: Update to 0.2.4-28.6699c15
Date: Mon, 16 May 2022 15:51:45 +0200 [thread overview]
Message-ID: <87pmkd8u1a.fsf_-_@gnu.org> (raw)
In-Reply-To: <3x0UR1PjJhbOj9nmgJBzCZ3h6GpydLeDXehH_EPG3Hbw-icJk3bFHpgv9spXH1Q4DNlH2ngTU0_EJaCb9wmBsZnMPUJDdM6_2f9mKiCrrQ0=@proton.me> (Sughosha@proton.me's message of "Sun, 08 May 2022 21:41:46 +0000")
Hi,
Sughosha <Sughosha@proton.me> skribis:
> Sorry, one small correction to the above (a comment was containing misleading version number)..
>
> ---
> gnu/packages/gnome.scm | 4 +-
> .../gcolor3-update-libportal-usage.patch | 55 +++++++++++++++++++
> 2 files changed, 58 insertions(+), 1 deletion(-)
> create mode 100644 gnu/packages/patches/gcolor3-update-libportal-usage.patch
I added the new file to ‘gnu/local.mk’, including a conventional commit
log, and pushed as commit 5ba12f0176300d154b086485ecf363f10f283a9f.
Please take a look at
<https://guix.gnu.org/manual/devel/en/html_node/Submitting-Patches.html>
if unsure about the project conventions. I’d also encourage you to send
patches with ‘git send-email’—pasting them in your mail client might
mangle them.
Thank you and thanks Daniel for taking a look!
Ludo’.
next prev parent reply other threads:[~2022-05-16 13:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 19:49 [bug#55295] [PATCH] gnu: gcolor3: Update to 0.2.4-28.6699c15 Sughosha via Guix-patches via
2022-05-07 10:00 ` Daniel Meißner via Guix-patches via
2022-05-08 21:21 ` [bug#55295] [PATCH] gnu: gcolor3: Fix build with libportal-0.5 Sughosha via Guix-patches via
2022-05-08 21:41 ` Sughosha via Guix-patches via
2022-05-16 13:51 ` Ludovic Courtès [this message]
2022-05-11 13:04 ` [bug#55295] [PATCH] gnu: gcolor3: Update to 0.2.4-28.6699c15 Daniel Meißner 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
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=87pmkd8u1a.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=55295-done@debbugs.gnu.org \
--cc=Sughosha@proton.me \
--cc=daniel.meissner-i4k@ruhr-uni-bochum.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 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).