all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 54678@debbugs.gnu.org, 54678-done@debbugs.gnu.org,
	jgart <jgart@dismail.de>
Subject: [bug#54678] [PATCH v2] gnu: Add emacs-pyimport.
Date: Fri, 10 Jun 2022 11:08:31 +0200	[thread overview]
Message-ID: <87tu8sq41c.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <e91830ec5bced3ba0925b0e48d48dddb8b944a83.camel@telenet.be> (Maxime Devos's message of "Wed, 08 Jun 2022 09:52:01 +0200")

Hello,

Maxime Devos <maximedevos@telenet.be> writes:

> reopen 54678
> thanks
>
> Nicolas Goaziou schreef op wo 08-06-2022 om 00:15 [+0200]:
>> jgart via Guix-patches via <guix-patches@gnu.org> writes:
>> 
>> > * gnu/packages/emacs-xyz.scm (emacs-pyimport): New variable.
>> 
>> Applied. Thank you.
>
> What about <https://issues.guix.gnu.org/54678#3>?

I asked a similar question for a different package some months (years?)
ago. The decision was that we should assume good faith from the author,
even if the licensing is not perfect. In this situation, upstream intent
is clear, so there is no real issue.

Of course, it would be nice to help upstream have a correct licensing
process.

Regards,
-- 
Nicolas Goaziou




  reply	other threads:[~2022-06-10 10:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-02  2:58 [bug#54678] [PATCH] gnu: Add emacs-pyimport jgart via Guix-patches via
2022-04-04 18:14 ` Maxime Devos
2022-04-05 20:48 ` [bug#54678] [PATCH v2] " jgart via Guix-patches via
2022-05-09 17:49   ` Maxime Devos
2022-06-07 22:15   ` Nicolas Goaziou
2022-06-08  7:52     ` Maxime Devos
2022-06-10  9:08       ` Nicolas Goaziou [this message]
2022-06-10 15:05         ` Maxime Devos

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=87tu8sq41c.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=54678-done@debbugs.gnu.org \
    --cc=54678@debbugs.gnu.org \
    --cc=jgart@dismail.de \
    --cc=maximedevos@telenet.be \
    /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.