Github messages for voidlinux
 help / color / mirror / Atom feed
From: Piraty <Piraty@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New package: megapixels-1.3.0
Date: Sun, 10 Jul 2022 23:57:37 +0200	[thread overview]
Message-ID: <20220710215737.-AKV6nZhkffZKsO7hem7-PI12fr_H85xesObox6ITVg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29129@inbox.vuxu.org>

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

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

New package: megapixels-1.3.0
https://github.com/void-linux/void-packages/pull/29129

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?
- [ ] 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.)
- [ ] 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-07-10 21:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-28 20:29 [PR PATCH] New package: megapixels-0.15.0 jcgruenhage
2021-10-14 21:04 ` Piraty
2021-10-14 21:13 ` jcgruenhage
2022-05-05  2:09 ` github-actions
2022-05-10 15:31 ` [PR PATCH] [Updated] " jcgruenhage
2022-05-10 18:40 ` New package: megapixels-1.3.0 jcgruenhage
2022-05-11 22:36 ` Piraty
2022-05-12  5:46 ` jcgruenhage
2022-05-12  9:52 ` [PR PATCH] [Updated] " jcgruenhage
2022-05-12 10:23 ` jcgruenhage
2022-05-13 19:12 ` [PR REVIEW] " paper42
2022-05-14  8:12 ` jcgruenhage
2022-05-16 19:23 ` Piraty
2022-05-16 19:24 ` [PR REVIEW] " Piraty
2022-05-16 19:25 ` Piraty
2022-05-16 19:28 ` Piraty
2022-07-10 21:57 ` Piraty [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=20220710215737.-AKV6nZhkffZKsO7hem7-PI12fr_H85xesObox6ITVg@z \
    --to=piraty@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).