From: ericonr <firstname.lastname@example.org> To: email@example.com Subject: Re: [PR PATCH] [Merged]: starship: update to 1.2.1 Date: Sun, 16 Jan 2022 19:59:34 +0100 [thread overview] Message-ID: <20220116185934.FOH4CHWpWwKbedNRSP_ONZam9YpvjL7mrZA_xsegkpI@z> (raw) In-Reply-To: <firstname.lastname@example.org> [-- Attachment #1: Type: text/plain, Size: 1059 bytes --] There's a merged pull request on the void-packages repository starship: update to 1.2.1 https://github.com/void-linux/void-packages/pull/34850 Description: <!-- Uncomment relevant sections and delete options which are not applicable --> #### Testing the changes - I tested the changes in this PR: **YES** <!-- #### New package - This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO** --> <!-- Note: If the build is likely to take more than 2 hours, please [skip CI](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:[~2022-01-16 18:59 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-04 20:27 [PR PATCH] starship: update to 1.1.1 cinerea0 2022-01-05 7:23 ` ericonr 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 ` ericonr [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=20220116185934.FOH4CHWpWwKbedNRSP_ONZam9YpvjL7mrZA_xsegkpI@z \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PR PATCH] [Merged]: starship: update to 1.2.1' \ /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
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).