GNU bug report logs - #36536
[PATCH] Update i3blocks to 1.4-2

Previous Next

Package: guix-patches;

Reported by: ison <ison <at> airmail.cc>

Date: Sun, 7 Jul 2019 11:18:01 UTC

Severity: normal

Tags: patch

Done: Ludovic Courtès <ludo <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: ison <ison <at> airmail.cc>
Subject: bug#36536: closed (Re: [bug#36536] [PATCH] Update i3blocks to 1.4-2)
Date: Mon, 08 Jul 2019 11:03:02 +0000
[Message part 1 (text/plain, inline)]
Your bug report

#36536: [PATCH] Update i3blocks to 1.4-2

which was filed against the guix-patches package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 36536 <at> debbugs.gnu.org.

-- 
36536: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=36536
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: Ludovic Courtès <ludo <at> gnu.org>
To: ison <ison <at> airmail.cc>
Cc: 36536-done <at> debbugs.gnu.org
Subject: Re: [bug#36536] [PATCH] Update i3blocks to 1.4-2
Date: Mon, 08 Jul 2019 13:02:31 +0200
Hi,

ison <ison <at> airmail.cc> 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 <ison <at> airmail.cc>
> 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’.

[Message part 3 (message/rfc822, inline)]
From: ison <ison <at> airmail.cc>
To: guix-patches <at> gnu.org
Subject: [PATCH] Update i3blocks to 1.4-2
Date: Sun, 7 Jul 2019 05:17:07 -0600
[Message part 4 (text/plain, inline)]
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 (text/plain, attachment)]

This bug report was last modified 6 years and 39 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.