From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: rustup: generate shell completions for cargo
Date: Tue, 22 Feb 2022 18:00:37 +0100 [thread overview]
Message-ID: <20220222170037.3uMZImMoCa9wxc3ZTDQtPfPi-i6FyL2hg8RnV9QgFUw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35768@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 279 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/pull/35768#issuecomment-1048011478
Comment:
This would conflict with the `cargo` package. Wouldn't it be better anyways to generate them using the selected toolchain on your system?
next prev parent reply other threads:[~2022-02-22 17:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 11:28 [PR PATCH] " tranzystorek-io
2022-02-22 17:00 ` Duncaen [this message]
2022-02-22 17:59 ` tranzystorek-io
2022-02-23 5:37 ` [PR PATCH] [Updated] " tranzystorek-io
2022-02-27 13:40 ` tranzystorek-io
2022-03-04 15:28 ` tranzystorek-io
2022-03-08 13:49 ` [PR PATCH] [Updated] " tranzystorek-io
2022-03-08 14:21 ` Duncaen
2022-03-08 15:26 ` tranzystorek-io
2022-03-08 16:15 ` Duncaen
2022-03-08 16:23 ` Duncaen
2022-03-08 16:47 ` tranzystorek-io
2022-06-28 2:15 ` [WIP] " github-actions
2022-06-28 5:06 ` [PR PATCH] [Updated] " tranzystorek-io
2022-06-28 5:22 ` tranzystorek-io
2022-07-15 6:00 ` [PR PATCH] [Updated] " tranzystorek-io
2022-07-15 6:31 ` tranzystorek-io
2022-07-15 6:46 ` tranzystorek-io
2022-07-15 10:40 ` jcgruenhage
2022-07-17 20:57 ` CameronNemo
2022-07-17 21:14 ` CameronNemo
2022-07-17 21:14 ` CameronNemo
2022-07-18 7:15 ` jcgruenhage
2022-07-18 22:29 ` [PR PATCH] [Updated] " tranzystorek-io
2022-07-20 15:27 ` ahesford
2022-07-20 15:34 ` Duncaen
2022-07-20 16:48 ` ahesford
2022-07-20 16:48 ` ahesford
2022-10-19 2:14 ` github-actions
2022-10-19 18:13 ` tranzystorek-io
2022-10-19 18:13 ` [PR PATCH] [Closed]: " tranzystorek-io
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=20220222170037.3uMZImMoCa9wxc3ZTDQtPfPi-i6FyL2hg8RnV9QgFUw@z \
--to=duncaen@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).