From: OliveThePuffin <OliveThePuffin@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: Updated ceres-solver to 2.1.0_1
Date: Sat, 22 Jul 2023 08:38:38 +0200 [thread overview]
Message-ID: <20230722063838.2HSFKRjUKxaiWD8gq9w4JGnSahByOYJtNzeBcjNnD7Y@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45184@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]
There's a closed pull request on the void-packages repository
Updated ceres-solver to 2.1.0_1
https://github.com/void-linux/void-packages/pull/45184
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**|**briefly**|**NO**
- briefly
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
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)
- x86_64-glibc
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl (crossbuilt on x86_64-glibc)
- It has the same bug as described in #45166 in both this version and the current version in repo (2.0.0_2)
- (I'd fix it myself if I knew how to)
- otherwise works well
next prev parent reply other threads:[~2023-07-22 6:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-22 1:00 [PR PATCH] Updated ceres-solver to 2.1.0_2 OliveThePuffin
2023-07-22 6:32 ` [PR PATCH] [Updated] " OliveThePuffin
2023-07-22 6:37 ` [PR PATCH] [Updated] Updated ceres-solver to 2.1.0_1 OliveThePuffin
2023-07-22 6:38 ` OliveThePuffin [this message]
2023-07-22 6:38 ` OliveThePuffin
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=20230722063838.2HSFKRjUKxaiWD8gq9w4JGnSahByOYJtNzeBcjNnD7Y@z \
--to=olivethepuffin@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).