From: Simon Tournier <zimon.toutoune@gmail.com>
To: Andy Tai <atai@atai.org>, 61010@debbugs.gnu.org
Subject: [bug#61010] [PATCH] gnu: Add icewm
Date: Tue, 24 Jan 2023 13:26:14 +0100 [thread overview]
Message-ID: <87k01cp195.fsf@gmail.com> (raw)
In-Reply-To: <CAJsg1E_sqTdfO7aFTfD3MGLv2RqiYs=m2YhjgHOUD8jx=C2OMg@mail.gmail.com>
Hi,
Thanks for the follow up. :-)
The patch builds fine and it LTGM except one minor point.
On dim., 22 janv. 2023 at 12:37, Andy Tai <atai@atai.org> wrote:
> + (source (origin
> + (method url-fetch)
> + (uri (string-append
> + "https://github.com/ice-wm/icewm/releases/download/"
> + version "/icewm-" version ".tar.lz"))
This archive contains generated .gmo which are not in the source code
[1] and I do not know what is the usual Guix policy about that. Do we
re-generate them?
Other said, these files are in the archive tar.gz [2].
1: <https://github.com/ice-wm/icewm/tree/3.3.1/po>
2: <https://github.com/ice-wm/icewm/archive/refs/tags/3.3.1.tar.gz>
> \ No newline at end of file
This patch does not apply to current master. From my point of view, it
is worth to provide the base-commit (see --base option of
git-format-patch or git-send-email).
And it helps if the new package is not added to the end of the file.
For instance, I would put it between i3lock-fancy and xmonad-next.
Cheers,
simon
next prev parent reply other threads:[~2023-01-24 13:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-22 20:37 [bug#61010] [PATCH] gnu: Add icewm Andy Tai
2023-01-23 17:33 ` [bug#61010] Andy Tai
2023-01-24 12:26 ` Simon Tournier [this message]
2023-01-25 7:37 ` [bug#61010] [PATCH] gnu: Add icewm Andy Tai
2023-01-25 7:50 ` Andy Tai
2023-01-25 9:21 ` Simon Tournier
2023-01-26 6:02 ` Andy Tai
2023-01-27 20:42 ` Andy Tai
2023-01-28 8:22 ` [bug#61010] [PATCH v3] " Andy Tai
2023-02-10 2:05 ` bug#61010: [PATCH] " 宋文武 via Guix-patches via
2023-02-06 11:43 ` [bug#61010] lost gtk input Feng Shu
2023-02-10 5:48 ` 宋文武 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=87k01cp195.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=61010@debbugs.gnu.org \
--cc=atai@atai.org \
/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.