all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Guillaume Le Vaillant <glv@posteo.net>
To: Jai Vetrivelan <jaivetrivelan@gmail.com>
Cc: 54254@debbugs.gnu.org
Subject: [bug#54254] [PATCH] gnu: dunst: Update to 1.8.1.
Date: Sat, 05 Mar 2022 12:22:20 +0000	[thread overview]
Message-ID: <877d9837tc.fsf@kitej> (raw)
In-Reply-To: <87ee3h53wz.fsf@gmail.com>

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


Jai Vetrivelan <jaivetrivelan@gmail.com> skribis:

> [1. text/patch; 0001-gnu-dunst-Update-to-1.8.1.patch]
> From af0d5b8381f9fec21ac01f88ca5f6384643a19b2 Mon Sep 17 00:00:00 2001
> From: Jai Vetrivelan <jaivetrivelan@gmail.com>
> Date: Sat, 5 Mar 2022 11:19:43 +0530
> Subject: [PATCH] gnu: dunst: Update to 1.8.1.
>
> * gnu/packages/dunst.scm (dunst): Update to 1.8.1.
> * gnu/packages/patches/dunst-1.7.3-fix-crash.patch: Remove patch file.
> ---
>  gnu/packages/dunst.scm                        |  6 +++---
>  .../patches/dunst-1.7.3-fix-crash.patch       | 21 -------------------
>  2 files changed, 3 insertions(+), 24 deletions(-)
>  delete mode 100644 gnu/packages/patches/dunst-1.7.3-fix-crash.patch
>
> [...]

Hi,

When removing a patch file, you also have to remove it from the list of
patches in "gnu/local.mk".
Can you send an updated patch?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2022-03-05 12:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-05  6:06 [bug#54254] [PATCH] gnu: dunst: Update to 1.8.1 Jai Vetrivelan
2022-03-05 12:22 ` Guillaume Le Vaillant [this message]
2022-03-05 13:31   ` Jai Vetrivelan
2022-03-16 14:14     ` bug#54254: " Ludovic Courtès
2022-03-05 12:33 ` [bug#54254] " 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=877d9837tc.fsf@kitej \
    --to=glv@posteo.net \
    --cc=54254@debbugs.gnu.org \
    --cc=jaivetrivelan@gmail.com \
    /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.