Github messages for voidlinux
 help / color / mirror / Atom feed
From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: New package: helvum-0.3.4
Date: Mon, 14 Mar 2022 08:08:32 +0100	[thread overview]
Message-ID: <20220314070832.vfNiTFK7jQmvyD7oUnPm-sgF94xLyV5Wi5er0gYB8tk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35591@inbox.vuxu.org>

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

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

New package: helvum-0.3.4
https://github.com/void-linux/void-packages/pull/35591

Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->

closes #35582
closes #34560

#### 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
-->


      parent reply	other threads:[~2022-03-14  7:08 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-13 18:44 [PR PATCH] " classabbyamp
2022-02-13 19:11 ` [PR PATCH] [Updated] " classabbyamp
2022-02-13 20:06 ` classabbyamp
2022-02-13 20:19 ` classabbyamp
2022-02-13 20:35 ` dkwo
2022-02-13 20:38 ` dkwo
2022-02-13 21:15 ` [PR PATCH] [Updated] " classabbyamp
2022-02-13 21:18 ` classabbyamp
2022-02-14  0:31 ` [PR PATCH] [Updated] " classabbyamp
2022-02-14  3:17 ` classabbyamp
2022-02-14  3:18 ` classabbyamp
2022-02-14  9:41 ` dkwo
2022-02-14 16:05 ` classabbyamp
2022-02-15 12:25 ` dkwo
2022-02-19 22:24 ` 0x5c
2022-02-19 22:31 ` classabbyamp
2022-02-20  0:27 ` 0x5c
2022-02-20  1:15 ` [PR PATCH] [Updated] " classabbyamp
2022-02-20  2:00 ` classabbyamp
2022-02-20  8:04 ` 0x5c
2022-02-20 21:32 ` classabbyamp
2022-02-24  5:07 ` [PR PATCH] [Updated] " classabbyamp
2022-02-24  5:47 ` classabbyamp
2022-02-24 20:30 ` classabbyamp
2022-02-27 22:34 ` [PR REVIEW] " paper42
2022-02-27 22:34 ` paper42
2022-02-27 22:57 ` [PR PATCH] [Updated] " classabbyamp
2022-02-27 22:58 ` [PR REVIEW] " classabbyamp
2022-02-27 22:58 ` [PR PATCH] [Updated] " classabbyamp
2022-03-05 23:01 ` classabbyamp
2022-03-06  3:14 ` classabbyamp
2022-03-13 22:54 ` [PR REVIEW] " paper42
2022-03-13 23:20 ` [PR PATCH] [Updated] " classabbyamp
2022-03-13 23:21 ` [PR REVIEW] " classabbyamp
2022-03-13 23:22 ` [PR PATCH] [Updated] " classabbyamp
2022-03-14  7:08 ` paper42 [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=20220314070832.vfNiTFK7jQmvyD7oUnPm-sgF94xLyV5Wi5er0gYB8tk@z \
    --to=paper42@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).