unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Elad Lahav <e2lahav@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 43234@debbugs.gnu.org
Subject: bug#43234: Patch: Fix QNX build in 28.x
Date: Tue, 8 Sep 2020 10:22:17 -0400	[thread overview]
Message-ID: <CAJbg=FV9unr8TOWNwV2APQxUbKvwSGR7CecZuFGJO3HgzKDwTA@mail.gmail.com> (raw)
In-Reply-To: <83mu20mk3i.fsf@gnu.org>

Couple of days?! C'mon... I can't wait that long!

Sorry, I didn't mean to sound impatient or ungrateful. I do appreciate
the help and responsiveness of the team, especially on an issue that
really affects only a handful of people (and I'm being generous with
"handful").

--Elad

On Tue, 8 Sep 2020 at 10:14, Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: Elad Lahav <e2lahav@gmail.com>
> > Date: Mon, 7 Sep 2020 20:10:42 -0400
> > Cc: Eli Zaretskii <eliz@gnu.org>, 43234@debbugs.gnu.org
> >
> > The fix has been pushed to the config project. What's the process for
> > pulling that into Emacs?
>
> The process is for you to sit tight and wait for a couple of days,
> until we have time to install your changes ;-).
>
> > Also, what happens with the fix to configure.ac? Should I submit that
> > separately?
>
> No need, we will use the part of the patch that you already submitted.
>
> Thanks.





  reply	other threads:[~2020-09-08 14:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-05 22:05 bug#43234: Patch: Fix QNX build in 28.x Elad Lahav
2020-09-06 14:24 ` Eli Zaretskii
2020-09-06 17:05   ` Andreas Schwab
2020-09-06 17:10     ` Elad Lahav
2020-09-08  0:10       ` Elad Lahav
2020-09-08 14:14         ` Eli Zaretskii
2020-09-08 14:22           ` Elad Lahav [this message]
2020-09-10 22:02           ` Lars Ingebrigtsen
2021-03-12  1:07             ` Stefan Kangas
2021-03-13  1:48               ` Elad Lahav
2021-03-13  2:44                 ` Stefan Kangas
2020-09-06 17:05   ` Elad Lahav

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/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJbg=FV9unr8TOWNwV2APQxUbKvwSGR7CecZuFGJO3HgzKDwTA@mail.gmail.com' \
    --to=e2lahav@gmail.com \
    --cc=43234@debbugs.gnu.org \
    --cc=eliz@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.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).