From: Leo Famulari <leo@famulari.name>
To: 44978@debbugs.gnu.org
Subject: [bug#44978] Package v 0.1.30 in preparation for 0.2
Date: Thu, 24 Dec 2020 17:03:28 -0500 [thread overview]
Message-ID: <X+UQMGTmNX68aS8S@jasmine.lan> (raw)
In-Reply-To: <0gb0j1LPUXE1LC-eLcvFAXxU5JJrfE3cMVV7-J-V_AWNgow8BD6wYScfdSzpoVlDVWm6suW-uSLNEv7fhT9U6cjzuK1khaZVducfpAIqRYg=@protonmail.com>
On Thu, Dec 24, 2020 at 02:44:57AM +0000, Ryan Prior via Guix-patches via wrote:
> Hi there! Bumping this again since vlang recently released 0.2, a major release has has a number of goodies I've asked for to help improve the quality of our package. I'm beginning the work to update our package to 0.2, and hopefully will also succeed at moving a few more of the vendored sources out into dedicated packages.
>
> If I can get any feedback on this patch series it would be very appreciated!
It looks like some parts of the patch series have been pushed. Can you
clarify what remains to be done? For example, attach your proposed
further work to a reply message.
next prev parent reply other threads:[~2020-12-24 22:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 1:44 [bug#44978] [PATCH] gnu: packages: Add tiny-bignum Ryan Prior via Guix-patches via
2020-12-01 4:10 ` [bug#44978] [PATCH] gnu: Add cjson Ryan Prior via Guix-patches via
2020-12-08 9:41 ` Christopher Baines
2020-12-01 4:15 ` [bug#44978] [PATCH 1/3] gnu: vlang: Update to 0.1.30 Ryan Prior via Guix-patches via
2020-12-01 4:15 ` [bug#44978] [PATCH 2/3] gnu: vlang: Use system tiny-bignum Ryan Prior via Guix-patches via
2020-12-01 4:15 ` [bug#44978] [PATCH 3/3] gnu: vlang: Use system cJSON Ryan Prior via Guix-patches via
2020-12-06 4:59 ` [bug#44978] Update vlang Ryan Prior via Guix-patches via
2020-12-08 9:40 ` [bug#44978] [PATCH] gnu: packages: Add tiny-bignum Christopher Baines
2020-12-24 2:44 ` [bug#44978] Package v 0.1.30 in preparation for 0.2 Ryan Prior via Guix-patches via
2020-12-24 22:03 ` Leo Famulari [this message]
2021-01-01 19:47 ` [bug#44978] What remains to be done for bug#44978 Ryan Prior 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
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=X+UQMGTmNX68aS8S@jasmine.lan \
--to=leo@famulari.name \
--cc=44978@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).