From: Brice Waegeneire <brice@waegenei.re>
To: 37928@debbugs.gnu.org
Subject: [bug#37928]
Date: Tue, 26 Nov 2019 21:17:20 +0100 [thread overview]
Message-ID: <20191126201721.7370-1-brice@waegenei.re> (raw)
In-Reply-To: <20191025202713.7739-2-brice@waegenei.re>
I have finally managed to write the requested tests.
string->license has been rewritten to output licenses instead of strings and to avoid swallowing unknown licenses. Now, importing rpigrep recursively give only 3 #f in the licenses fields.
next prev parent reply other threads:[~2019-11-26 20:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 20:27 [bug#37927] Brice Waegeneire
2019-10-25 20:27 ` [bug#37928] [PATCH] import: crate: Fix licenses Brice Waegeneire
2019-11-04 22:27 ` [bug#37927] " Ludovic Courtès
2019-11-16 16:37 ` Ludovic Courtès
2019-11-26 20:17 ` Brice Waegeneire [this message]
2019-11-26 20:17 ` [bug#37928] [PATCH v2] import: crate: Better handle license expressions Brice Waegeneire
2019-12-11 11:24 ` bug#37927: " 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=20191126201721.7370-1-brice@waegenei.re \
--to=brice@waegenei.re \
--cc=37928@debbugs.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).