From: "Ludovic Courtès" <ludo@gnu.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: wingo@igalia.com, deller@gmx.de, dave.anglin@bell.net,
guile-devel@gnu.org,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Subject: Re: [PATCH, v2] Fix build on platforms where the stack grows upwards
Date: Sat, 08 Feb 2020 15:07:39 +0100 [thread overview]
Message-ID: <874kw1yxxw.fsf@gnu.org> (raw)
In-Reply-To: <20200204121152.3335558-1-glaubitz@physik.fu-berlin.de> (John Paul Adrian Glaubitz's message of "Tue, 4 Feb 2020 13:11:53 +0100")
Hi,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> skribis:
> * libguile/continuations.c (scm_dynthrow): Fix missing mra
> parameter to grow_stack for SCM_STACK_GROWS_UP.
Applied, thanks!
Ludo'.
next prev parent reply other threads:[~2020-02-08 14:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 12:11 [PATCH, v2] Fix build on platforms where the stack grows upwards John Paul Adrian Glaubitz
2020-02-08 14:07 ` Ludovic Courtès [this message]
2020-03-10 22:58 ` John David Anglin
2020-03-13 16:29 ` Andy Wingo
2020-03-13 17:17 ` John David Anglin
2020-07-22 21:54 ` John Paul Adrian Glaubitz
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874kw1yxxw.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=dave.anglin@bell.net \
--cc=deller@gmx.de \
--cc=glaubitz@physik.fu-berlin.de \
--cc=guile-devel@gnu.org \
--cc=wingo@igalia.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.
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).