Github messages for voidlinux
 help / color / mirror / Atom feed
From: emacsomancer <emacsomancer@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] Picom v8
Date: Wed, 22 Apr 2020 01:41:28 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21230@inbox.vuxu.org> (raw)

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

There is a new pull request by emacsomancer against master on the void-packages repository

https://github.com/emacsomancer/void-packages picom-v8
https://github.com/void-linux/void-packages/pull/21230

Picom v8


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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-picom-v8-21230.patch --]
[-- Type: text/x-diff, Size: 1897 bytes --]

From c7aa3b96e63467546412604f9e20f050a37d3840 Mon Sep 17 00:00:00 2001
From: Benjamin Slade <slade@jnanam.net>
Date: Tue, 21 Apr 2020 13:45:02 -0600
Subject: [PATCH 1/2] merge mu template

---
 srcpkgs/mu/template | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/srcpkgs/mu/template b/srcpkgs/mu/template
index 78668f59da8..5fdd3a9ad45 100644
--- a/srcpkgs/mu/template
+++ b/srcpkgs/mu/template
@@ -12,6 +12,7 @@ license="GPL-3.0-or-later"
 homepage="https://www.djcbsoftware.nl/code/mu/"
 distfiles="https://github.com/djcb/mu/archive/${version}.tar.gz"
 checksum=66ae911abb3d7269514fada08e7a13ad61a205e10209055c41df2f9d17568274
+<<<<<<< HEAD
 
 if [ ! "$CROSS_BUILD" ]; then
 	subpackages="mu4e"
@@ -22,6 +23,8 @@ else
 	subpackages=" "
 	configure_args+=" --disable-mu4e"
 fi
+=======
+>>>>>>> 4f8783e0ec... mu: update to 1.4
 
 pre_configure() {
 	sed -i 's,-I${prefix}/include,,' contrib/Makefile.am

From 98e85b6c8ea7c1e015a32a47992c2aea9900d0da Mon Sep 17 00:00:00 2001
From: Benjamin Slade <slade@jnanam.net>
Date: Tue, 21 Apr 2020 17:40:42 -0600
Subject: [PATCH 2/2] picom: update to v8

---
 srcpkgs/picom/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/picom/template b/srcpkgs/picom/template
index aefb85b1d39..884f94e20c4 100644
--- a/srcpkgs/picom/template
+++ b/srcpkgs/picom/template
@@ -1,6 +1,6 @@
 # Template file for 'picom'
 pkgname=picom
-version=7.5
+version=8
 revision=1
 build_style=meson
 configure_args="-Dbuild_docs=true"
@@ -14,7 +14,7 @@ maintainer="Frank Steinborn <steinex@nognu.de>"
 license="MIT, MPL-2.0"
 homepage="https://github.com/yshui/picom/"
 distfiles="https://github.com/yshui/picom/archive/v${version}.tar.gz"
-checksum=1fdeda688d09643563e4314f885beaf074023235e56598ae98d481364e615607
+checksum=f839a3c058ca90f463eae3973a9381cf2fe93be7d0e58db1c28ea72acd10480f
 
 post_install() {
 	vlicense LICENSES/MIT

             reply	other threads:[~2020-04-21 23:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21 23:41 emacsomancer [this message]
2020-04-22  0:07 ` [PR PATCH] [Closed]: picom: update to v8 emacsomancer

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-21230@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).