From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: phodina <phodina@protonmail.com>, help-guix <help-guix@gnu.org>
Subject: Re: Crates versions and their replacement
Date: Tue, 5 Oct 2021 20:19:08 +0200 [thread overview]
Message-ID: <50766b90-5f3d-bb9d-c72f-367699e36b1a@crazy-compilers.com> (raw)
In-Reply-To: <_iKORBL8YRhY5YAb01lAkiuJHc2Tyt1WToJJfaKjmuoyYI-Ch4Rt_pJ4EM-5OOTHvPHQwTpKzZ1flPHjrrlPfoxp1_lAEpbohni8fknQXJs=@protonmail.com>
Am 03.10.21 um 09:02 schrieb phodina:
> Now comes the question. How often should it be use and what are the
> pros and cons?
I suggest to use this only if required, since versions are defined to
strict.
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
next prev parent reply other threads:[~2021-10-05 18:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 7:02 Crates versions and their replacement phodina
2021-10-05 18:19 ` Hartmut Goebel [this message]
2021-10-10 7:11 ` phodina
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=50766b90-5f3d-bb9d-c72f-367699e36b1a@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=help-guix@gnu.org \
--cc=phodina@protonmail.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.
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).