Github messages for voidlinux
 help / color / mirror / Atom feed
From: Shanduur <Shanduur@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: drone-runner-exec-1.0.0-beta.10
Date: Tue, 13 Sep 2022 17:08:11 +0200	[thread overview]
Message-ID: <20220913150811.TpvHbzRxch7lw8L-wXPlLxguJu0CAEFZ6QMcvNp1PC0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39245@inbox.vuxu.org>

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

There is an updated pull request by Shanduur against master on the void-packages repository

https://github.com/Shanduur/void-packages add-drone-runner-exec
https://github.com/void-linux/void-packages/pull/39245

New package: drone-runner-exec-1.0.0-beta.10
<!-- 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 [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **NO**

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
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, (x86_64-musl)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - aarch64

I want to keep and modify this PR in the future, when `drone-runner-exec` comes out of beta (hopefully soon). Up until this moment, consider this a WIP PR.

A patch file from https://github.com/void-linux/void-packages/pull/39245.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-add-drone-runner-exec-39245.patch --]
[-- Type: text/x-diff, Size: 0 bytes --]



  parent reply	other threads:[~2022-09-13 15:08 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-12 14:58 [PR PATCH] " Shanduur
2022-09-12 15:02 ` [PR PATCH] [Updated] " Shanduur
2022-09-12 15:04 ` Shanduur
2022-09-12 15:06 ` Shanduur
2022-09-12 15:20 ` Shanduur
2022-09-12 15:25 ` Shanduur
2022-09-12 17:37 ` [PR REVIEW] " classabbyamp
2022-09-12 17:37 ` classabbyamp
2022-09-13 14:37 ` [PR PATCH] [Updated] " Shanduur
2022-09-13 14:48 ` [PR REVIEW] " Shanduur
2022-09-13 14:50 ` [PR PATCH] [Updated] " Shanduur
2022-09-13 14:52 ` Shanduur
2022-09-13 14:53 ` Shanduur
2022-09-13 14:54 ` Shanduur
2022-09-13 14:54 ` Shanduur
2022-09-13 14:55 ` Shanduur
2022-09-13 14:55 ` Shanduur
2022-09-13 14:55 ` Shanduur
2022-09-13 15:08 ` [PR PATCH] [Closed]: " Shanduur
2022-09-13 15:08 ` Shanduur [this message]
2022-09-13 15:09 ` [PR PATCH] [Updated] " Shanduur
2022-12-13  2:03 ` github-actions
2022-12-28  1:56 ` [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=20220913150811.TpvHbzRxch7lw8L-wXPlLxguJu0CAEFZ6QMcvNp1PC0@z \
    --to=shanduur@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).