From: kitzman via Guix-patches via <guix-patches@gnu.org>
To: 54078@debbugs.gnu.org
Subject: [bug#54078] [PATCH 0/0] gnu: add libaml, libneatvnc, and wayvnc
Date: Mon, 21 Feb 2022 10:06:43 +0200 [thread overview]
Message-ID: <87fsocbq3w.fsf@disroot.org> (raw)
In-Reply-To: <87mtilb40o.fsf@disroot.org> (kitzman@disroot.org's message of "Sun, 20 Feb 2022 23:51:35 +0200")
I was missing some imports in gnu/packages/vnc.scm.
With this occasion I have also split my commit in three different ones.
kitzman <kitzman@disroot.org> writes:
> I have attached a patch for the following packages:
> - gnu/packages/linux.scm:8818 libaml
> - gnu/packages/vnc.scm:361 libneatvnc
> - gnu/packages/vnc.scm:384 wayvnc
>
> The libraries/software are created by a single person, with
> dependents/dependencies which are also created by them. I can
> split this into a patch set if deemed more appropriate.
next prev parent reply other threads:[~2022-02-21 8:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-20 21:51 [bug#54078] [PATCH] gnu: add libaml, libneatvnc, and wayvnc kitzman via Guix-patches via
2022-02-21 8:06 ` kitzman via Guix-patches via [this message]
2022-02-21 8:09 ` [bug#54078] [PATCH 1/3] gnu: add libaml kitzman via Guix-patches via
2022-02-21 13:12 ` Maxime Devos
2022-02-23 17:50 ` kitzman via Guix-patches via
2022-02-23 17:58 ` Maxime Devos
2022-02-23 18:50 ` kitzman via Guix-patches via
2022-02-21 8:11 ` [bug#54078] [PATCH 2/3] gnu: add libneatvnc kitzman via Guix-patches via
2022-02-21 13:22 ` Maxime Devos
2022-02-23 18:57 ` [bug#54078] [PATCH] gnu: add libaml, libneatvnc, and wayvnc kitzman via Guix-patches via
2022-02-23 19:15 ` Maxime Devos
2022-02-23 21:02 ` kitzman via Guix-patches via
2022-02-21 8:12 ` [bug#54078] [PATCH 3/3] gnu: add wayvnc kitzman via Guix-patches via
2022-02-23 21:04 ` kitzman 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=87fsocbq3w.fsf@disroot.org \
--to=guix-patches@gnu.org \
--cc=54078@debbugs.gnu.org \
--cc=kitzman@disroot.org \
/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.