--- Begin Message ---
|
Subject: |
[PATCH] Update i3blocks to 1.4-2 |
|
Date: |
Sun, 7 Jul 2019 05:17:07 -0600 |
|
User-agent: |
NeoMutt/20180716 |
i3blocks click events weren't functioning with the latest i3bar.
Updating fixes the issue. See attached patch.
Sorry for the dumb quesiton, but I hope I am correctly understanding the role of
"revision" here. I simply incremented it from 1 to 2.
My understanding is it's just a number added to the end of the version string to
give it a unique value when updating to a commit that doesn't correspond to an
exact release.
If that's not correct then please let me know so I can fix it.
0001-Update-i3blocks-to-1.4-2.patch
Description: Text document
--- End Message ---
--- Begin Message ---
|
Subject: |
Re: [bug#36536] [PATCH] Update i3blocks to 1.4-2 |
|
Date: |
Mon, 08 Jul 2019 13:02:31 +0200 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux) |
Hi,
ison <address@hidden> skribis:
> i3blocks click events weren't functioning with the latest i3bar.
> Updating fixes the issue. See attached patch.
>
> Sorry for the dumb quesiton, but I hope I am correctly understanding the role
> of
> "revision" here. I simply incremented it from 1 to 2.
> My understanding is it's just a number added to the end of the version string
> to
> give it a unique value when updating to a commit that doesn't correspond to an
> exact release.
That’s correct!
>>From 0c0705d510db8e4c7f9e5a3ff8b1cbf48d6bc104 Mon Sep 17 00:00:00 2001
> From: ison <address@hidden>
> Date: Sun, 7 Jul 2019 05:02:01 -0600
> Subject: [PATCH] Update i3blocks to 1.4-2
>
> ---
> gnu/packages/wm.scm | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
I adjusted the commit log to match our conventions and applied it.
Thanks!
Ludo’.
--- End Message ---