From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] libpipeline: fix typo in license
Date: Fri, 20 Sep 2019 10:10:11 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14602@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 311 bytes --]
There is a new pull request by wezm against master on the void-packages repository
https://github.com/wezm/void-packages patch-1
https://github.com/void-linux/void-packages/pull/14602
libpipeline: fix typo in license
A patch file from https://github.com/void-linux/void-packages/pull/14602.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-patch-1-14602.patch --]
[-- Type: text/x-diff, Size: 914 bytes --]
From c0911c05e5cedf6eda91a0f7efe235131f8bdc9a Mon Sep 17 00:00:00 2001
From: Wesley Moore <wes@wezm.net>
Date: Fri, 20 Sep 2019 16:09:56 +0800
Subject: [PATCH] libpipeline: fix typo in license
---
srcpkgs/libpipeline/template | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/srcpkgs/libpipeline/template b/srcpkgs/libpipeline/template
index e5e28d79434..b1ffab2d00c 100644
--- a/srcpkgs/libpipeline/template
+++ b/srcpkgs/libpipeline/template
@@ -6,7 +6,7 @@ build_style=gnu-configure
checkdepends="check-devel pkg-config"
short_desc="Pipeline manipulation library"
maintainer="Orphaned <orphan@voidlinux.org>"
-license="GPL-3.0-or-alter"
+license="GPL-3.0-or-later"
homepage="http://libpipeline.nongnu.org/"
distfiles="https://download-mirror.savannah.gnu.org/releases/libpipeline/libpipeline-${version}.tar.gz"
checksum=d633706b7d845f08b42bc66ddbe845d57e726bf89298e2cee29f09577e2f902f
next reply other threads:[~2019-09-20 8:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 8:10 voidlinux-github [this message]
2019-09-21 12:14 ` [PR PATCH] [Merged]: " voidlinux-github
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14602@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--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).