From: "宋文武 via Guix-patches via" <guix-patches@gnu.org>
To: phodina <phodina@protonmail.com>
Cc: 57608-done@debbugs.gnu.org
Subject: bug#57608: Upstreaming KDE Plasma and rest of packages
Date: Sat, 02 Sep 2023 12:23:25 +0800 [thread overview]
Message-ID: <87h6odryo2.fsf@envs.net> (raw)
In-Reply-To: <sbaRaktLZuhBxV8-S2T-niKNLa5qmLze0H4uBCzWFYTqwcs72027gnDYSatFh8xYVBa1BVnJxVovSWXYnmK1bH44dSuGBSve5eOS9yOq8O4=@protonmail.com> (phodina@protonmail.com's message of "Tue, 06 Sep 2022 07:14:39 +0000")
phodina <phodina@protonmail.com> writes:
> [...]
>
> The patches are again tracked in the branch patch/upstream-kde [2]. Expect rebases as my next plan is to go
> through licenses and later tests + builds.
Hello, we have a working KDE plasma in master now, closing.
If there are still some changes needed, please rebase and open new
issues, thanks!
prev parent reply other threads:[~2023-09-02 4:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 7:14 [bug#57608] Upstreaming KDE Plasma and rest of packages phodina via Guix-patches via
2022-09-19 17:50 ` phodina via Guix-patches via
2022-09-24 13:12 ` Ludovic Courtès
2022-09-24 13:15 ` Ludovic Courtès
2022-10-02 17:14 ` guix-patches--- via
2022-10-04 6:52 ` phodina via Guix-patches via
2022-10-04 11:07 ` guix-patches--- via
2022-10-04 14:01 ` phodina via Guix-patches via
2022-10-06 12:09 ` phodina via Guix-patches via
2022-10-06 18:29 ` kiasoc5 via Guix-patches via
2022-10-07 12:57 ` phodina via Guix-patches via
2022-10-07 14:09 ` Maxim Cournoyer
2022-10-10 13:03 ` guix-patches--- via
2022-11-21 21:11 ` Marius Bakke
2022-11-22 10:20 ` phodina via Guix-patches via
2022-11-22 10:56 ` Marius Bakke
2022-12-27 21:15 ` phodina via Guix-patches via
2022-12-28 0:48 ` Maxim Cournoyer
2022-10-29 11:59 ` Brendan Tildesley
2022-10-29 20:32 ` guix-patches--- via
2022-10-29 23:49 ` Brendan Tildesley
2022-10-31 7:42 ` phodina via Guix-patches via
2023-09-02 4:23 ` 宋文武 via Guix-patches via [this message]
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=87h6odryo2.fsf@envs.net \
--to=guix-patches@gnu.org \
--cc=57608-done@debbugs.gnu.org \
--cc=iyzsong@envs.net \
--cc=phodina@protonmail.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.