From: Tobias Geerinckx-Rice via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: Ryan Prior <rprior@protonmail.com>,
Ryan Prior via Guix-patches <guix-patches@gnu.org>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>, 45644@debbugs.gnu.org
Subject: Re: [bug#45644] closed (Re: [bug#45644] [PATCH] gnu: esbuild: Update to 0.8.29.)
Date: Mon, 04 Jan 2021 18:07:35 +0100 [thread overview]
Message-ID: <87im8cfx60.fsf@nckx> (raw)
In-Reply-To: <8735zgmy81.fsf@nckx>
[-- Attachment #1: Type: text/plain, Size: 640 bytes --]
Tobias Geerinckx-Rice 写道：
> I can't say what went wrong, only that I routinely apply patches
> from
> Guix MLs through mu4e and ‘git am’ without trouble. I
> think. The last
> ~dozen patches signed off by me seem fine, at least.
...no idea why I didn't actually test your actual patch that
caused this actual question.
commit e258898862f38aa9effa33ddae7fc517b0a403f4 (HEAD -> tmp)
Author: Ryan Prior via Guix-patches via <guix-patches@gnu.org>
gnu: Add picoev.
* gnu/packages/networking.scm (picoev): New variable.
Signed-off-by: Tobias Geerinckx-Rice <me@tobias.gr>
Eh,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2021-01-04 17:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 1:47 [bug#45644] [PATCH] gnu: esbuild: Update to 0.8.29 Ryan Prior via Guix-patches via
2021-01-04 1:56 ` Leo Famulari
[not found] ` <handler.45644.D45644.160972538318518.notifdone@debbugs.gnu.org>
2021-01-04 2:47 ` [bug#45644] closed (Re: [bug#45644] [PATCH] gnu: esbuild: Update to 0.8.29.) Ryan Prior via Guix-patches via
2021-01-04 17:02 ` Tobias Geerinckx-Rice via Development of GNU Guix and the GNU System distribution.
2021-01-04 17:07 ` Tobias Geerinckx-Rice via Development of GNU Guix and the GNU System distribution. [this message]
2021-01-04 17:56 ` Leo Famulari
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=87im8cfx60.fsf@nckx \
--to=guix-devel@gnu.org \
--cc=45644@debbugs.gnu.org \
--cc=guix-patches@gnu.org \
--cc=me@tobias.gr \
--cc=rprior@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 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).