From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: kicad: update to 6.0.1
Date: Fri, 28 Jan 2022 07:27:34 +0100 [thread overview]
Message-ID: <20220128062734.jGNnw-kkF0gyg8DMEh04lCMkYXr-QC_6smEE3GytR2o@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34917@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]
There's a closed pull request on the void-packages repository
kicad: update to 6.0.1
https://github.com/void-linux/void-packages/pull/34917
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**/**briefly**: I opened a project of mine, looked around and made some minor edits, tried the main components (schematic editor, PCB editor, 3D viewer), but I didn't test *all* features (scripting, gerber output with weird contents, SPICE integration, ...).
[ci skip] because `kicad-packages3D` is humongous, and KiCAD itself takes a long while to build, and all other packages are trivial (only assets).
#### Local build testing
- I built this PR locally for my native architecture, x86_64-glibc
- I did **not** build this PR locally for these architectures as I don't have any of these machines (thus cannot test it) and cross-compiling would take too long.
So, preferably, a few other people should test this PR as well.
next prev parent reply other threads:[~2022-01-28 6:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 2:47 [PR PATCH] kicad: update to 6.0.0 PoroCYon
2022-01-07 18:52 ` unspecd
2022-01-07 23:07 ` [PR PATCH] [Updated] " PoroCYon
2022-01-07 23:10 ` PoroCYon
2022-01-16 8:43 ` lemmi
2022-01-16 8:44 ` lemmi
2022-01-16 16:37 ` [PR PATCH] [Updated] " PoroCYon
2022-01-16 16:38 ` PoroCYon
2022-01-16 17:48 ` kicad: update to 6.0.1 PoroCYon
2022-01-16 18:35 ` [PR REVIEW] " ericonr
2022-01-16 18:35 ` ericonr
2022-01-16 18:35 ` ericonr
2022-01-16 23:33 ` PoroCYon
2022-01-16 23:39 ` PoroCYon
2022-01-17 0:55 ` [PR PATCH] [Updated] " PoroCYon
2022-01-17 0:57 ` PoroCYon
2022-01-17 4:47 ` [PR REVIEW] " ericonr
2022-01-17 17:17 ` [PR PATCH] [Updated] " PoroCYon
2022-01-23 22:23 ` PoroCYon
2022-01-26 17:26 ` foopub
2022-01-26 17:34 ` foopub
2022-01-27 0:32 ` PoroCYon
2022-01-27 1:05 ` PoroCYon
2022-01-27 13:53 ` [PR PATCH] [Updated] " PoroCYon
2022-01-28 6:27 ` ericonr [this message]
2022-01-28 8:00 ` ericonr
2022-01-29 1:12 ` foopub
2022-01-29 1:12 ` foopub
2022-01-23 16:33 [PR PATCH] " foopub
2022-01-23 17:38 ` [PR PATCH] [Closed]: " foopub
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=20220128062734.jGNnw-kkF0gyg8DMEh04lCMkYXr-QC_6smEE3GytR2o@z \
--to=ericonr@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).