From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: libgit2: update to 1.7.2
Date: Thu, 28 Mar 2024 15:13:41 +0100 [thread overview]
Message-ID: <20240328141341.40DBD2163C@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45976@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]
There's a merged pull request on the void-packages repository
libgit2: update to 1.7.2
https://github.com/void-linux/void-packages/pull/45976
Description:
[ci skip]
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
Todos:
- [x] cargo-edit
- [x] cargo-outdated
Related pending PRs:
- #45829
- #45972
- #45853 Ping @cinerea0
- #46043
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- 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)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
prev parent reply other threads:[~2024-03-28 14:13 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 17:43 [PR PATCH] [WIP] libgit2: update to 1.7.1 tranzystorek-io
2023-09-12 13:10 ` [PR PATCH] [Updated] " tranzystorek-io
2023-09-17 8:46 ` tranzystorek-io
2023-09-17 13:25 ` tranzystorek-io
2023-10-05 16:15 ` tranzystorek-io
2023-11-26 15:47 ` tranzystorekk
2023-12-01 5:33 ` icp1994
2023-12-01 12:54 ` [PR PATCH] [Updated] " tranzystorekk
2023-12-01 13:14 ` tranzystorekk
2023-12-01 16:32 ` tranzystorekk
2024-02-07 12:15 ` [PR PATCH] [Updated] " tranzystorekk
2024-02-07 12:32 ` [PR PATCH] [Updated] [WIP] libgit2: update to 1.7.2 tranzystorekk
2024-02-12 14:05 ` leahneukirchen
2024-02-12 14:35 ` tranzystorekk
2024-02-12 16:07 ` leahneukirchen
2024-02-12 16:09 ` leahneukirchen
2024-02-12 16:40 ` tranzystorekk
2024-02-12 17:30 ` [PR PATCH] [Updated] " tranzystorekk
2024-02-17 13:08 ` tranzystorekk
2024-02-20 17:03 ` tranzystorekk
2024-02-24 11:15 ` tranzystorekk
2024-02-24 11:17 ` tranzystorekk
2024-03-01 14:20 ` tranzystorekk
2024-03-01 15:45 ` tranzystorekk
2024-03-18 15:02 ` tranzystorekk
2024-03-18 16:55 ` tranzystorekk
2024-03-20 16:44 ` tranzystorekk
2024-03-22 8:44 ` tranzystorekk
2024-03-22 22:24 ` [PR PATCH] [Updated] " tranzystorekk
2024-03-23 6:41 ` tranzystorekk
2024-03-23 20:56 ` tranzystorekk
2024-03-24 12:06 ` tranzystorekk
2024-03-25 22:49 ` tranzystorekk
2024-03-26 12:54 ` tranzystorekk
2024-03-26 17:18 ` tranzystorekk
2024-03-28 14:13 ` cinerea0 [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=20240328141341.40DBD2163C@inbox.vuxu.org \
--to=cinerea0@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).