From: "Ludovic Courtès" <ludo@gnu.org>
To: 51493-done@debbugs.gnu.org
Subject: bug#51493: [PATCH 0/5] Improvements to the pypi, cran, and "print" importers
Date: Thu, 11 Nov 2021 00:26:50 +0100 [thread overview]
Message-ID: <87lf1vfv7p.fsf@gnu.org> (raw)
In-Reply-To: <20211029212948.30148-1-ludo@gnu.org> ("Ludovic Courtès"'s message of "Fri, 29 Oct 2021 23:29:48 +0200")
Ludovic Courtès <ludo@gnu.org> skribis:
> import: pypi: Allow imports of a specific version.
> import: cran: Allow imports of a specific version.
> import: print: Properly render packages with origins as inputs.
> import: print: Correctly handle URI lists.
> import: print: Handle patches that are origins.
Pushed as b2ed40c29f578d46d42cb1c5e99bd797cea3aba0, topped with this
extra commit in the same vein:
3756ce3267 import: print: Replace packages and origins in 'arguments'.
I’ll have to take care of the merge conflicts with ‘core-updates-frozen’
in print.scm…
Ludo’.
prev parent reply other threads:[~2021-11-10 23:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 21:29 [bug#51493] [PATCH 0/5] Improvements to the pypi, cran, and "print" importers Ludovic Courtès
2021-10-29 21:35 ` [bug#51493] [PATCH 1/5] import: pypi: Allow imports of a specific version Ludovic Courtès
2021-10-29 21:35 ` [bug#51493] [PATCH 2/5] import: cran: " Ludovic Courtès
2021-10-29 21:35 ` [bug#51493] [PATCH 3/5] import: print: Properly render packages with origins as inputs Ludovic Courtès
2021-10-29 21:35 ` [bug#51493] [PATCH 4/5] import: print: Correctly handle URI lists Ludovic Courtès
2021-10-29 21:35 ` [bug#51493] [PATCH 5/5] import: print: Handle patches that are origins Ludovic Courtès
2021-11-12 10:18 ` [bug#51493] [PATCH 1/5] import: pypi: Allow imports of a specific version zimoun
2021-11-12 10:49 ` Tobias Geerinckx-Rice via Guix-patches via
2021-11-12 11:10 ` zimoun
2021-11-10 23:26 ` Ludovic Courtès [this message]
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=87lf1vfv7p.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=51493-done@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).