From: "Ludovic Courtès" <ludo@gnu.org>
To: Ivan Petkov <ivanppetkov@gmail.com>
Cc: 36514@debbugs.gnu.org
Subject: [bug#36514] [PATCH] gnu: rust: Update to 1.36.0.
Date: Thu, 11 Jul 2019 23:14:22 +0200 [thread overview]
Message-ID: <878st4p93l.fsf@gnu.org> (raw)
In-Reply-To: <97FF5CD4-6D68-4CA2-A806-41EB968A41EF@gmail.com> (Ivan Petkov's message of "Fri, 5 Jul 2019 10:21:59 -0700")
Hi Ivan,
Ivan Petkov <ivanppetkov@gmail.com> skribis:
> * gnu/packages/rust.scm (rust): Rename to...
> (rust-1.35): ...this.
> (rust): New variable.
It looks like a safe addition, I think you can go ahead!
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-07-11 21:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 17:21 [bug#36514] [PATCH] gnu: rust: Update to 1.36.0 Ivan Petkov
2019-07-11 21:14 ` Ludovic Courtès [this message]
2019-07-12 3:30 ` bug#36514: " Ivan Petkov
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=878st4p93l.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=36514@debbugs.gnu.org \
--cc=ivanppetkov@gmail.com \
/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).