From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: vscode: update to 1.65.1
Date: Wed, 16 Mar 2022 10:28:15 +0100 [thread overview]
Message-ID: <20220316092815.VlPn0xEn3M4vbjmb5iN3n2nI_yfkLM5T2lH6Q3-p-so@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35465@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1260 bytes --]
There's a merged pull request on the void-packages repository
vscode: update to 1.65.1
https://github.com/void-linux/void-packages/pull/35465
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
I changed q66's package to replace @vscode/ripgrep to a far simpler version that only exposes the correct path and thus should never need to change and also removes the requirement to copy over files.
prev parent reply other threads:[~2022-03-16 9:28 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 21:44 [PR PATCH] vscode: update to 1.64.0 atk
2022-02-12 20:51 ` tibequadorian
2022-02-12 20:53 ` tibequadorian
2022-02-14 8:22 ` [PR PATCH] [Updated] " atk
2022-02-14 8:23 ` atk
2022-02-14 8:26 ` [PR PATCH] [Updated] vscode: update to 1.64.2 atk
2022-02-20 11:44 ` [PR REVIEW] " paper42
2022-02-20 11:45 ` paper42
2022-02-22 8:15 ` [PR PATCH] [Updated] " atk
2022-02-22 8:15 ` [PR REVIEW] " atk
2022-02-22 10:37 ` atk
2022-02-22 10:45 ` atk
2022-02-27 20:47 ` atk
2022-02-27 20:49 ` [PR PATCH] [Updated] " atk
2022-03-07 12:48 ` atk
2022-03-08 20:45 ` [PR PATCH] [Updated] vscode: update to 1.65.0 atk
2022-03-11 8:37 ` [PR PATCH] [Updated] vscode: update to 1.65.1 atk
2022-03-11 8:41 ` atk
2022-03-13 21:59 ` [PR REVIEW] " paper42
2022-03-13 21:59 ` paper42
2022-03-13 22:02 ` paper42
2022-03-14 6:46 ` atk
2022-03-14 8:39 ` atk
2022-03-14 8:52 ` atk
2022-03-14 8:53 ` atk
2022-03-14 8:53 ` atk
2022-03-14 8:56 ` [PR PATCH] [Updated] " atk
2022-03-14 8:58 ` [PR REVIEW] " atk
2022-03-14 9:04 ` [PR PATCH] [Updated] " atk
2022-03-16 9:28 ` paper42 [this message]
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=20220316092815.VlPn0xEn3M4vbjmb5iN3n2nI_yfkLM5T2lH6Q3-p-so@z \
--to=paper42@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).