From: emacsomancer <emacsomancer@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] picom: restore manpages
Date: Thu, 23 Apr 2020 00:52:05 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21257@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 328 bytes --]
There is a new pull request by emacsomancer against master on the void-packages repository
https://github.com/emacsomancer/void-packages picom-missing-man
https://github.com/void-linux/void-packages/pull/21257
picom: restore manpages
A patch file from https://github.com/void-linux/void-packages/pull/21257.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-picom-missing-man-21257.patch --]
[-- Type: text/x-diff, Size: 799 bytes --]
From 46a3b6edf1ec3c0b82596568f77d1edae153cea0 Mon Sep 17 00:00:00 2001
From: Benjamin Slade <slade@jnanam.net>
Date: Wed, 22 Apr 2020 16:49:43 -0600
Subject: [PATCH] picom: restore manpages
---
srcpkgs/picom/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/picom/template b/srcpkgs/picom/template
index 884f94e20c4..8d3d9176471 100644
--- a/srcpkgs/picom/template
+++ b/srcpkgs/picom/template
@@ -1,9 +1,9 @@
# Template file for 'picom'
pkgname=picom
version=8
-revision=1
+revision=2
build_style=meson
-configure_args="-Dbuild_docs=true"
+configure_args="-Dwith_docs=true"
hostmakedepends="pkg-config asciidoc"
makedepends="MesaLib-devel dbus-devel libconfig-devel libev-devel pcre-devel
pixman-devel xcb-util-image-devel xcb-util-renderutil-devel
next reply other threads:[~2020-04-22 22:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 22:52 emacsomancer [this message]
2020-04-24 9:50 ` [PR PATCH] [Merged]: " leahneukirchen
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-21257@inbox.vuxu.org \
--to=emacsomancer@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).