From: tranzystorek-io <tranzystorek-io@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: cocogitto-4.1.0
Date: Fri, 04 Mar 2022 16:16:28 +0100 [thread overview]
Message-ID: <20220304151628.QR79p6nlCuM3QkOA61yJRbwe-6D2Ugml4ZOo297uKOI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35693@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 323 bytes --]
New comment by tranzystorek-io on void-packages repository
https://github.com/void-linux/void-packages/pull/35693#issuecomment-1059251635
Comment:
I wanted to make cocogitto use the system installation of `libgit2`, but internally the `git2` crate statically compiles a vendored version if the system version is `<1.1.0`
next prev parent reply other threads:[~2022-03-04 15:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-19 9:56 [PR PATCH] " tranzystorek-io
2022-02-19 18:18 ` [PR PATCH] [Updated] " tranzystorek-io
2022-02-20 16:05 ` tranzystorek-io
2022-02-26 11:39 ` tranzystorek-io
2022-02-27 12:19 ` tranzystorek-io
2022-03-04 14:08 ` tranzystorek-io
2022-03-04 15:14 ` tranzystorek-io
2022-03-04 15:16 ` tranzystorek-io [this message]
2022-03-05 10:30 ` tranzystorek-io
2022-03-08 13:49 ` tranzystorek-io
2022-03-09 7:52 ` tranzystorek-io
2022-03-09 8:39 ` New package: cocogitto-5.0.0 tranzystorek-io
2022-03-09 8:39 ` tranzystorek-io
2022-03-10 17:54 ` [PR PATCH] [Updated] " tranzystorek-io
2022-03-10 18:13 ` tranzystorek-io
2022-03-14 9:31 ` tranzystorek-io
2022-03-27 15:54 ` tranzystorek-io
2022-03-27 19:51 ` tranzystorek-io
2022-03-28 6:33 ` tranzystorek-io
2022-03-28 6:41 ` tranzystorek-io
2022-03-29 12:59 ` tranzystorek-io
2022-03-29 13:08 ` tranzystorek-io
2022-03-29 13:11 ` [PR PATCH] [Updated] New package: cocogitto-5.0.1 tranzystorek-io
2022-04-06 18:03 ` tranzystorek-io
2022-04-11 11:30 ` [PR PATCH] [Merged]: " Gottox
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=20220304151628.QR79p6nlCuM3QkOA61yJRbwe-6D2Ugml4ZOo297uKOI@z \
--to=tranzystorek-io@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).