From: "宋文武 via Guix-patches via" <guix-patches@gnu.org>
To: Feng Shu <tumashu@163.com>
Cc: 61056@debbugs.gnu.org
Subject: [bug#61056] [PATCH] gnu: Add jwm.
Date: Mon, 06 Mar 2023 15:46:32 +0800 [thread overview]
Message-ID: <874jqyqq3r.fsf_-_@envs.net> (raw)
In-Reply-To: <87mt5homto.fsf@163.com> (Feng Shu's message of "Mon, 13 Feb 2023 18:56:51 +0800")
Feng Shu <tumashu@163.com> writes:
> Hello:
>
> Please review v8 version of jwm/mjwm patch.
>
> Thanks
Hello, I have pushed jwm and mjwm with follow changes:
1. remove tango-icon-theme, mjwm, xterm from jwm's inputs. see 2.
2. remove patch-example.jwmrc and install-tango-icon-files phases.
I think those kind of customization better happend in ~/.jwmrc or
a home service.
3. change libxrandr to libxrender for jwm, as the latter is actually
used...
4. mjwm: remove '.' in synopsis, change license to 'license:gpl2+'.
What do you think of my changes in 1. and 2.?
next prev parent reply other threads:[~2023-03-06 7:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 11:15 [bug#61056] [PATCH] gnu: Add jwm tumashu
2023-01-27 11:05 ` [bug#61056] [PATCH v2] " tumashu
2023-01-27 11:07 ` [bug#61056] jwm version Feng Shu
2023-01-28 11:37 ` [bug#61056] [PATCH] gnu: Add mjwm tumashu
2023-01-29 11:12 ` [bug#61056] [PATCH v3 1/2] gnu: Add jwm tumashu
2023-01-29 11:12 ` [bug#61056] [PATCH v3 2/2] gnu: Add mjwm tumashu
2023-01-29 11:12 ` [bug#61056] [PATCH v4 1/2] gnu: Add jwm Feng Shu
2023-01-29 11:12 ` [bug#61056] [PATCH v4 2/2] gnu: Add mjwm Feng Shu
2023-02-11 2:30 ` [bug#61056] [PATCH v5 1/2] gnu: Add jwm tumashu
2023-02-11 2:30 ` [bug#61056] [PATCH v5 2/2] gnu: Add mjwm tumashu
2023-02-11 2:55 ` [bug#61056] [PATCH v6 1/2] gnu: Add jwm tumashu
2023-02-11 2:55 ` [bug#61056] [PATCH v6 2/2] gnu: Add mjwm tumashu
2023-02-13 7:16 ` [bug#61056] [PATCH v7 1/2] gnu: Add jwm Feng Shu
2023-02-13 7:17 ` [bug#61056] [PATCH v7 2/2] gnu: Add mjwm Feng Shu
2023-02-13 10:45 ` [bug#61056] [PATCH v8 1/2] gnu: Add jwm Feng Shu
2023-02-13 10:45 ` [bug#61056] [PATCH v8 2/2] gnu: Add mjwm Feng Shu
2023-02-13 10:49 ` [bug#61056] [PATCH v8 1/2] gnu: Add jwm Feng Shu
2023-02-13 10:49 ` [bug#61056] [PATCH v8 2/2] gnu: Add mjwm Feng Shu
2023-02-13 10:56 ` [bug#61056] Please review v8 version of jwm/mjwm patch Feng Shu
2023-03-06 7:46 ` 宋文武 via Guix-patches via [this message]
2023-03-06 8:04 ` [bug#61056] [PATCH] gnu: Add jwm 宋文武 via Guix-patches via
2023-03-06 12:11 ` Feng Shu
2023-03-07 1:08 ` bug#61056: " 宋文武 via Guix-patches via
2023-02-28 22:04 ` [bug#61056] " Feng Shu
2023-03-06 7:47 ` [bug#61056] [PATCH 1/2] " iyzsong--- via Guix-patches via
2023-03-06 7:47 ` [bug#61056] [PATCH 2/2] gnu: Add mjwm iyzsong--- via Guix-patches via
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=874jqyqq3r.fsf_-_@envs.net \
--to=guix-patches@gnu.org \
--cc=61056@debbugs.gnu.org \
--cc=iyzsong@envs.net \
--cc=tumashu@163.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.