From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: libgit2: update to 1.2.0.
Date: Tue, 21 Jun 2022 04:13:03 +0200 [thread overview]
Message-ID: <20220621021303.o3s5kwYoh8R0QruCL1r-N1pE2QB-A6LK5vx4pMAJyT8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33535@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1776 bytes --]
There's a closed pull request on the void-packages repository
libgit2: update to 1.2.0.
https://github.com/void-linux/void-packages/pull/33535
Description:
Updated libgit2 to `v1.2.0`, added patch with PR
https://github.com/libgit2/libgit2/pull/6032 of
`git_remote_name_is_valid` fix for https://github.com/libgit2/git2go/issues/834 issue.
<!-- Mark items with [x] where applicable -->
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me: checked with tests of https://github.com/libgit2/git2go (`libgit2` is a dependency there)
- [ ] I generally don't use the affected packages but briefly tested this PR
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [x] I built this PR locally for my native architecture, (ARCH-LIBC) (built, installed and tested)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
-->
Ref: #28456
Maintainer: @q66
prev parent reply other threads:[~2022-06-21 2:13 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 7:10 [PR PATCH] " g4s8
2021-10-14 16:25 ` q66
2021-10-15 6:39 ` [PR PATCH] [Updated] " g4s8
2021-10-15 7:16 ` g4s8
2021-10-15 7:20 ` g4s8
2021-10-15 13:36 ` [PR REVIEW] " ericonr
2021-10-15 13:36 ` ericonr
2021-10-15 13:36 ` ericonr
2021-10-15 13:40 ` ericonr
2021-10-15 14:13 ` q66
2021-10-15 14:14 ` q66
2021-10-15 14:42 ` g4s8
2021-10-15 15:28 ` q66
2021-10-15 16:35 ` g4s8
2021-10-18 9:13 ` [PR PATCH] [Updated] " g4s8
2021-10-19 6:17 ` g4s8
2021-10-19 6:17 ` g4s8
2021-10-19 6:17 ` g4s8
2021-10-19 13:44 ` q66
2021-10-19 14:10 ` [PR PATCH] [Updated] " g4s8
2021-10-19 15:40 ` g4s8
2021-10-25 7:13 ` g4s8
2021-10-26 5:39 ` g4s8
2021-11-15 14:46 ` g4s8
2021-11-17 9:49 ` g4s8
2021-11-17 15:36 ` q66
2021-11-18 6:34 ` [PR PATCH] [Updated] " g4s8
2022-06-07 2:12 ` github-actions
2022-06-21 2:13 ` github-actions [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=20220621021303.o3s5kwYoh8R0QruCL1r-N1pE2QB-A6LK5vx4pMAJyT8@z \
--to=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).