From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: starship: update to 1.1.1
Date: Wed, 05 Jan 2022 08:23:55 +0100 [thread overview]
Message-ID: <20220105072355.o7ef6-Q690ZUIg6YTUUi_bHi3c-gu4_vRLPFtDCqtko@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34850@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 195 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/34850#issuecomment-1005442238
Comment:
Ah, so same issue as `mdcat` and `delta` for cross :/
next prev parent reply other threads:[~2022-01-05 7:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 20:27 [PR PATCH] " cinerea0
2022-01-05 7:23 ` ericonr [this message]
2022-01-14 17:01 ` [PR PATCH] [Updated] " cinerea0
2022-01-14 17:33 ` starship: update to 1.2.0 cinerea0
2022-01-15 17:39 ` [PR PATCH] [Updated] " cinerea0
2022-01-15 19:11 ` starship: update to 1.2.1 ericonr
2022-01-16 18:59 ` [PR PATCH] [Merged]: " ericonr
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=20220105072355.o7ef6-Q690ZUIg6YTUUi_bHi3c-gu4_vRLPFtDCqtko@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).