From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: "Frédéric Martinsons" <frederic.martinsons@gmail.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [bitbake-devel] [PATCH] fetch:crate: create versioned 'name' entries
Date: Wed, 05 Apr 2023 14:24:15 +0200 [thread overview]
Message-ID: <lycz4icya8.fsf@ensc-pc.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <CA+cAkerceUTAyZ6DveoQF1d-i4nHg6f64UJ2PUr-=L0igeCsFg@mail.gmail.com> ("Frédéric Martinsons"'s message of "Wed, 5 Apr 2023 14:21:52 +0200")
Frédéric Martinsons <frederic.martinsons@gmail.com> writes:
> A rust project must have a Cargo.lock in its source (
> https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
It is recommended (due to documentation issues), but not required.
Enrico
next prev parent reply other threads:[~2023-04-05 12:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 10:16 [PATCH] fetch:crate: create versioned 'name' entries Enrico Scholz
2023-04-05 12:03 ` [bitbake-devel] " Frédéric Martinsons
2023-04-05 12:09 ` Enrico Scholz
2023-04-05 12:21 ` Frédéric Martinsons
2023-04-05 12:24 ` Enrico Scholz [this message]
2023-04-05 12:50 ` Frédéric Martinsons
[not found] ` <17530ADB1695B5D1.3977@lists.openembedded.org>
2023-04-05 16:28 ` Frédéric Martinsons
2023-04-05 16:44 ` Enrico Scholz
2023-04-05 17:05 ` Frédéric Martinsons
2023-04-06 8:45 ` Richard Purdie
2023-04-06 10:05 ` Frédéric Martinsons
2023-04-06 10:15 ` Richard Purdie
2023-04-06 10:20 ` Enrico Scholz
2023-04-06 12:14 ` Richard Purdie
2023-04-06 13:00 ` Frédéric Martinsons
2023-04-06 13:44 ` Richard Purdie
2023-04-06 13:57 ` Frédéric Martinsons
2023-04-06 14:01 ` Enrico Scholz
2023-04-06 14:18 ` ';sha256sum=' attribute in SRC_URI (was: [bitbake-devel] [PATCH] fetch:crate: create versioned 'name' entries) Enrico Scholz
2023-04-06 14:46 ` Frédéric Martinsons
2023-04-05 12:21 ` [PATCH, v2] fetch2/crate: create versioned 'name' entries Enrico Scholz
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=lycz4icya8.fsf@ensc-pc.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--cc=bitbake-devel@lists.openembedded.org \
--cc=frederic.martinsons@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.