From: jgart via Guix-patches via <guix-patches@gnu.org>
To: phodina <phodina@protonmail.com>
Cc: "49619@debbugs.gnu.org" <49619@debbugs.gnu.org>,
Sarah Morgensen <iskarian@mgsn.dev>,
Lars-Dominik Braun <lars@6xq.net>
Subject: [bug#49619] Upstream or close the ticket
Date: Sun, 30 Oct 2022 17:23:03 -0500 [thread overview]
Message-ID: <20221030172303.GB15447@dismail.de> (raw)
In-Reply-To: <nes0GJ47W_qRA-Z46_msG4REzB7pUywCaPovHhGKCl2RcqOyFVstPponD6wQqkweBy28NIJX1wFXI7ESQQaPcRdzM7o9MQjk5bzv2kBNBrU=@protonmail.com>
On Sun, 30 Oct 2022 20:22:35 +0000 phodina <phodina@protonmail.com> wrote:
> Is it technically all right and can it be upstreamed or should it be closed due to being tied to "non-libre" service?
>
The fact that this software interacts with a "non-libre" service/backend should not be a blocker for Guix.
all best,
jgart
next prev parent reply other threads:[~2022-10-30 22:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-18 11:36 [bug#49619] [PATCH 1/2] Add pirate-get phodina via Guix-patches via
2021-07-21 2:53 ` Sarah Morgensen
2021-07-22 12:17 ` phodina via Guix-patches via
2021-07-22 12:22 ` [bug#49619] [PATCH 2/2] " phodina via Guix-patches via
2021-09-18 8:07 ` [bug#49619] Patch status phodina via Guix-patches via
2021-09-18 12:44 ` [bug#49619] [PATCH v3 1/2] gnu: Add python-very-pretty-table phodina via Guix-patches via
2021-09-18 12:45 ` [bug#49619] [PATCH v3 2/2] gnu: Add python-pirate-get phodina via Guix-patches via
2021-11-08 16:52 ` phodina via Guix-patches via
2021-09-22 3:21 ` [bug#49619] [PATCH v3 1/2] gnu: Add python-very-pretty-table Sarah Morgensen
2021-09-27 22:41 ` phodina via Guix-patches via
2022-10-30 20:22 ` [bug#49619] Upstream or close the ticket phodina via Guix-patches via
2022-10-30 22:23 ` jgart via Guix-patches via [this message]
2022-12-25 18:01 ` phodina 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=20221030172303.GB15447@dismail.de \
--to=guix-patches@gnu.org \
--cc=49619@debbugs.gnu.org \
--cc=iskarian@mgsn.dev \
--cc=jgart@dismail.de \
--cc=lars@6xq.net \
--cc=phodina@protonmail.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.