From: Mark H Weaver <mhw@netris.org>
To: Isaac Jurado <diptongo@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: Feedback for #21076
Date: Mon, 17 Jun 2019 11:10:10 -0400 [thread overview]
Message-ID: <87imt49rjh.fsf@netris.org> (raw)
In-Reply-To: <CALqPu36HfOyrsAwLnieu_yPaXiVcT9JktHZxiUo64T4ZYm4s_Q@mail.gmail.com> (Isaac Jurado's message of "Mon, 17 Jun 2019 10:57:10 +0200")
Hi Isaac,
Isaac Jurado <diptongo@gmail.com> writes:
> Thanks! There's no rush. But I wanted to merge it before 2.2.5
I'm sorry, but it's unlikely to be included in 2.2.5, which will be
released very soon. I won't have time to investigate the issues around
your proposed patch before then.
Mark
next prev parent reply other threads:[~2019-06-17 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-16 17:53 Feedback for #21076 Isaac Jurado
2019-06-16 21:04 ` Mark H Weaver
2019-06-17 8:57 ` Isaac Jurado
2019-06-17 15:10 ` Mark H Weaver [this message]
2019-06-17 15:57 ` Isaac Jurado
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=87imt49rjh.fsf@netris.org \
--to=mhw@netris.org \
--cc=diptongo@gmail.com \
--cc=guile-devel@gnu.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.
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).