Github messages for voidlinux
 help / color / mirror / Atom feed
From: nezos <nezos@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New Package: gmt-6.1_1
Date: Sun, 18 Apr 2021 18:19:48 +0200	[thread overview]
Message-ID: <20210418161948.lF_c36Iq7phFVpY8oNemiQitbO0BcIBt1mYi9vNVmHM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30299@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1419 bytes --]

There's a closed pull request on the void-packages repository

New Package: gmt-6.1_1
https://github.com/void-linux/void-packages/pull/30299

Description:
<!-- Mark items with [x] where applicable -->

#### General
- [X] 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
- [ ] 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, (x86_64-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl


  reply	other threads:[~2021-04-18 16:19 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-18 16:14 [PR PATCH] " nezos
2021-04-18 16:19 ` nezos [this message]
2021-04-18 16:36 ` [PR PATCH] [Updated] " nezos
2021-04-18 17:41 ` [PR PATCH] [Closed]: " nezos
2021-04-18 18:05 ` [PR PATCH] [Updated] " nezos
2021-04-18 18:07 ` nezos
2021-04-18 19:06 ` nezos
2021-04-18 19:14 ` nezos
2021-04-18 20:24 ` ericonr
2021-04-18 20:27 ` Duncaen
2021-04-18 21:27 ` [PR PATCH] [Updated] " nezos
2021-04-18 22:08 ` nezos
2021-04-18 22:20 ` nezos
2021-04-20 14:09 ` nezos
2021-04-21 15:31 ` [PR REVIEW] " ericonr
2021-04-21 20:36 ` [PR PATCH] [Closed]: " nezos
2021-04-21 20:36 ` [PR PATCH] [Updated] " nezos
2021-04-21 20:55 ` nezos
2021-04-21 20:58 ` [PR PATCH] [Closed]: " nezos
2021-04-21 20:58 ` [PR PATCH] [Updated] " nezos
2021-04-21 21:11 ` nezos
2021-04-21 21:18 ` nezos
2021-04-26 18:02 ` [PR PATCH] [Updated] " nezos
2022-05-18  2:09 ` github-actions
2022-06-01  2:14 ` [PR PATCH] [Closed]: " github-actions

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=20210418161948.lF_c36Iq7phFVpY8oNemiQitbO0BcIBt1mYi9vNVmHM@z \
    --to=nezos@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).