unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: Simon South <simon@simonsouth.net>
Cc: 51241@debbugs.gnu.org
Subject: [bug#51241] [PATCH 0/1] gnu: ragel: Fix build of knot on aarch64-linux.
Date: Sat, 16 Oct 2021 19:42:30 +0200	[thread overview]
Message-ID: <87pms4c17r.fsf@nckx> (raw)
In-Reply-To: <cover.1634402642.git.simon@simonsouth.net>

[-- Attachment #1: Type: text/plain, Size: 350 bytes --]

Simon,

Thanks for taking care of Knot.  The changes themselves LGTM.

Simon South 写道：
> With the patch applied

Mmm, that's some very raw diff! :-)

Is this an (applied?) upstream patch?  Or did you write it, and if 
so, have you submitted it for upstream inclusion anywhere its 
progress can be tracked?

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  parent reply	other threads:[~2021-10-16 17:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-16 17:04 [bug#51241] [PATCH 0/1] gnu: ragel: Fix build of knot on aarch64-linux Simon South
2021-10-16 17:06 ` [bug#51241] [PATCH 1/1] " Simon South
2021-10-16 17:42 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2021-10-16 20:09   ` [bug#51241] [PATCH 0/1] " Simon South
2021-10-16 21:37     ` Tobias Geerinckx-Rice via Guix-patches via
2021-11-12 20:44 ` [bug#51241] [PATCH v2 " Simon South
2021-11-12 20:44   ` [bug#51241] [PATCH v2 1/1] " Simon South
2021-12-19 22:30     ` [bug#51241] [PATCH 0/1] " Ludovic Courtès
2021-12-20 22:57       ` Simon South
2021-12-21  9:12         ` Ludovic Courtès
2021-12-29 17:46           ` Simon South
2021-12-29 17:46             ` [bug#51241] [PATCH 1/1] " Simon South
2021-12-31 17:29               ` bug#51241: " Ludovic Courtès

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=87pms4c17r.fsf@nckx \
    --to=guix-patches@gnu.org \
    --cc=51241@debbugs.gnu.org \
    --cc=me@tobias.gr \
    --cc=simon@simonsouth.net \
    /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).