From: "Miguel Ángel Moreno" <mail@migalmoreno.com>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: mail@migalmoreno.com, "Ludovic Courtès" <ludo@gnu.org>,
62201@debbugs.gnu.org, "Andrew Tropin" <andrew@trop.in>
Subject: [bug#62201] [PATCH] gnu: Add payload-dumper.
Date: Fri, 30 Jun 2023 10:52:13 +0200 [thread overview]
Message-ID: <86jzvlbade.fsf@migalmoreno.com> (raw)
In-Reply-To: <3c0e73e6fab7fbb8394f509a427315aee6f299a6.camel@gmail.com> (Liliana Marie Prikler's message of "Thu, 29 Jun 2023 18:59:08 +0200")
On 2023-06-29 18:59, Liliana Marie Prikler wrote:
> Am Donnerstag, dem 29.06.2023 um 17:14 +0400 schrieb Andrew Tropin:
>> On 2023-06-28 09:51, Miguel Ángel Moreno wrote:
>>
>> > Hi Andrew,
>> >
>> > Thanks for having a look. I raised an issue on the repo, but
>> > the maintainer told me he isn't the original author of the tool and
>> > thus doesn't feel comfortable adding a license to it, see
>> > <https://github.com/vm03/payload_dumper/issues/58>. How should we
>> > proceed in this case?
>>
>> I would summon more advanced in this topic colleagues :)
>>
>> CCed Ludo and Liliana.
> No license, no original source? No, thanks.
> For more background, see [1,2].
>
> Cheers
>
> [1] https://www.gnu.org/licenses/license-list.html#NoLicense
> [2] https://www.gnu.org/licenses/license-list.html.en#NoLicense
Thanks for the heads up. Unless Ludo or someone else has some pointers
on what could be done to tackle this scenario, I'll try to package this
elsewhere.
--
Best regards,
Miguel Ángel Moreno
next prev parent reply other threads:[~2023-06-30 8:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 12:34 [bug#62201] [PATCH] gnu: Add payload-dumper conses
2023-06-13 10:58 ` Andrew Tropin
2023-06-28 7:51 ` Miguel Ángel Moreno
2023-06-29 13:14 ` Andrew Tropin
2023-06-29 16:59 ` Liliana Marie Prikler
2023-06-30 8:52 ` Miguel Ángel Moreno [this message]
2023-07-10 21:29 ` bug#62201: " Ludovic Courtès
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=86jzvlbade.fsf@migalmoreno.com \
--to=mail@migalmoreno.com \
--cc=62201@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=liliana.prikler@gmail.com \
--cc=ludo@gnu.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 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).