all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>,
	Jai Vetrivelan <jaivetrivelan@gmail.com>
Cc: 54252@debbugs.gnu.org
Subject: [bug#54252] [PATCH] gnu: lemonbar: Update to 1.4.
Date: Fri, 11 Mar 2022 08:28:38 +0100	[thread overview]
Message-ID: <b8e16592a8e80d2bc9db29b994a3611eca682357.camel@telenet.be> (raw)
In-Reply-To: <87bkyd48ny.fsf@nicolasgoaziou.fr>

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

Nicolas Goaziou schreef op vr 11-03-2022 om 01:47 [+0100]:
> Jai Vetrivelan <jaivetrivelan@gmail.com> writes:
> 
> > From dedefb5d5f0389d1e6fb190c9d47a6f8ca398791 Mon Sep 17 00:00:00 2001
> > From: Jai Vetrivelan <jaivetrivelan@gmail.com>
> > Date: Sat, 5 Mar 2022 11:17:57 +0530
> > Subject: [PATCH] gnu: lemonbar: Update to 1.4.
> 
> Applied. Thank you.

I don't think the null pointer dereferences have been reported upstream
yet.

Greetings,
Maxime

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2022-03-11  7:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-05  6:05 [bug#54252] [PATCH] gnu: lemonbar: Update to 1.4 Jai Vetrivelan
2022-03-05  9:59 ` Maxime Devos
     [not found]   ` <87h78c4knq.fsf@gmail.com>
2022-03-05 15:32     ` Maxime Devos
2022-03-11 12:32   ` Maxime Devos
2022-03-05 10:01 ` Maxime Devos
2022-03-11  0:47 ` bug#54252: " Nicolas Goaziou
2022-03-11  7:28   ` Maxime Devos [this message]
2022-03-11  8:31     ` [bug#54252] " Nicolas Goaziou
2022-03-11 19:15       ` Maxim Cournoyer
2022-03-11 22:09         ` Nicolas Goaziou
2022-03-11 22:30           ` Maxime Devos
2022-03-11 23:14             ` Nicolas Goaziou
2022-03-11 23:26               ` Maxime Devos

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=b8e16592a8e80d2bc9db29b994a3611eca682357.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=54252@debbugs.gnu.org \
    --cc=jaivetrivelan@gmail.com \
    --cc=mail@nicolasgoaziou.fr \
    /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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.