From: "Ludovic Courtès" <ludo@gnu.org>
To: Prafulla Giri <pratheblackdiamond@gmail.com>
Cc: 43198-done@debbugs.gnu.org
Subject: bug#43198: Add breeze icon assets
Date: Wed, 09 Sep 2020 09:26:34 +0200 [thread overview]
Message-ID: <87zh5zmmvp.fsf@gnu.org> (raw)
In-Reply-To: <CAFw+=j0Nyv58hcC_6mtzeYt=wgETcPYyRKBj4acba4rgZaw5zg@mail.gmail.com> (Prafulla Giri's message of "Tue, 8 Sep 2020 16:56:00 +0545")
Hi,
Prafulla Giri <pratheblackdiamond@gmail.com> skribis:
> From 8096401f6f977cf48b66914e161da0efd124931e Mon Sep 17 00:00:00 2001
> From: Prafulla Giri <pratheblackdiamond@gmail.com>
> Date: Fri, 4 Sep 2020 12:56:26 +0545
> Subject: [PATCH 1/2] gnu: kde-frameworks: Add breeze-assets
>
> * gnu/packages/kde-frameworks.scm (breeze-assets): New variable.
Applied.
> From b7d4e572923a98cc4ff266e95a3bd247556fb834 Mon Sep 17 00:00:00 2001
> From: Prafulla Giri <pratheblackdiamond@gmail.com>
> Date: Fri, 4 Sep 2020 12:59:28 +0545
> Subject: [PATCH 2/2] gnu: kde-frameworks: Add breeze
>
> * gnu/packages/kde-frameworks.scm (breeze): New variable.
[...]
> + (synopsis "Full Breeze Theme")
> + (description "The full Breeze visual style: a union-build of
> +breeze-assets and breeze-icons.")
I tweaked these and applied it.
Thank you!
Ludo’.
PS: Please keep the bug Cc’d.
next prev parent reply other threads:[~2020-09-09 7:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 8:22 [bug#43198] Add breeze icon assets Prafulla Giri
2020-09-04 9:29 ` Ludovic Courtès
[not found] ` <CAFw+=j2GyvfVWw-qsR1ju4+CEVAzhfP7p6hociAfF1YcBDOuSg@mail.gmail.com>
2020-09-04 11:00 ` [bug#43198] Fwd: " Prafulla Giri
2020-09-07 8:06 ` Ludovic Courtès
2020-09-08 11:11 ` Prafulla Giri
2020-09-08 11:25 ` [bug#43198] Fwd: " Prafulla Giri
2020-09-09 7:26 ` Ludovic Courtès [this message]
2020-09-09 8:27 ` Prafulla Giri
2020-10-26 19:07 ` [bug#43198] Questions about "Add breeze icon assets" Hartmut Goebel
2020-10-27 4:35 ` Prafulla Giri
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zh5zmmvp.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=43198-done@debbugs.gnu.org \
--cc=pratheblackdiamond@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).