From: teldra <teldra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] drone-cli: update to 1.4.0.
Date: Wed, 06 Oct 2021 10:23:05 +0200 [thread overview]
Message-ID: <20211006082305.KlkQoIjvWI36AQe1ct6540nZCIdu3jdWcXy5refnLOM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33368@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 462 bytes --]
There is an updated pull request by teldra against master on the void-packages repository
https://github.com/teldra/void-packages update-drone-cli
https://github.com/void-linux/void-packages/pull/33368
drone-cli: update to 1.4.0.
#### Have the results of the proposed changes been tested?
- [x] I generally don't use the affected packages but briefly tested this PR
A patch file from https://github.com/void-linux/void-packages/pull/33368.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update-drone-cli-33368.patch --]
[-- Type: text/x-diff, Size: 1111 bytes --]
From d44b34aec9b80769b82cbc4021bac4a6beadfe50 Mon Sep 17 00:00:00 2001
From: teldra <teldra@rotce.de>
Date: Wed, 6 Oct 2021 08:21:47 +0200
Subject: [PATCH] drone-cli: update to 1.4.0.
---
srcpkgs/drone-cli/template | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/drone-cli/template b/srcpkgs/drone-cli/template
index 36f4191696da..44885976b677 100644
--- a/srcpkgs/drone-cli/template
+++ b/srcpkgs/drone-cli/template
@@ -1,6 +1,6 @@
# Template file for 'drone-cli'
pkgname=drone-cli
-version=1.3.0
+version=1.4.0
revision=1
build_style=go
go_import_path=github.com/drone/drone-cli
@@ -10,5 +10,6 @@ short_desc="CLI for Drone continuous delivery platform"
maintainer="teldra <teldra@rotce.de>"
license="Apache-2.0"
homepage="https://github.com/drone/drone-cli"
+changelog="https://raw.githubusercontent.com/drone/drone-cli/master/CHANGELOG.md"
distfiles="https://github.com/drone/drone-cli/archive/v${version}.tar.gz"
-checksum=e5e61d9e9fb3556c7c2b05cbe8254904a59ba49707aff0ef57b1a5223d051f8c
+checksum=6b19378c923f71303dc753f2d39e7126285c23a504d20e3ce35fa8ee5605db03
next prev parent reply other threads:[~2021-10-06 8:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 6:50 [PR PATCH] " teldra
2021-10-06 8:11 ` [PR REVIEW] " paper42
2021-10-06 8:22 ` [PR PATCH] [Updated] " teldra
2021-10-06 8:22 ` [PR REVIEW] " teldra
2021-10-06 8:23 ` teldra [this message]
2021-10-07 2:20 ` [PR PATCH] [Merged]: " ericonr
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=20211006082305.KlkQoIjvWI36AQe1ct6540nZCIdu3jdWcXy5refnLOM@z \
--to=teldra@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).