From: Patrick Brennan <pbrennan@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: npostavs@gmail.com, 34688@debbugs.gnu.org
Subject: bug#34688: 26.1; Crash on Pasting from Windows clipboard
Date: Mon, 1 Apr 2019 20:45:21 -0700 [thread overview]
Message-ID: <CAB5xGOHq_cGd4=W-jRExEt5y_aCwmVEugermt-A5G-nr48c8Ew@mail.gmail.com> (raw)
In-Reply-To: <834l7hgn0s.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]
Not necessarily. If it was a Windows build issue, that code is still
hanging around on a Windows branch and may well find its way into
production. I think closing the big is therefore premature.
On Mon, Apr 1, 2019, 7:26 PM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Patrick Brennan <pbrennan@gmail.com>
> > Date: Mon, 1 Apr 2019 12:32:18 -0700
> > Cc: Noam Postavsky <npostavs@gmail.com>, 34688@debbugs.gnu.org
> >
> > That was my feeling as well - that there were potentially new changes
> which were released only to the Insider
> > Ring (which I'm in), and which break Emacs. Therefore I thought it was a
> good idea to post the bug now, so
> > that if it turns out that this really is Emacs-breaking, you have some
> lead time to address it. I reverted my last
> > update, though, and I believe I have taken at last one build since then,
> but I haven't seen it come back.
>
> Then I guess what you saw was a one-time issue with that particular
> build of Windows, and we can now close this bug?
>
[-- Attachment #2: Type: text/html, Size: 1553 bytes --]
next prev parent reply other threads:[~2019-04-02 3:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 18:13 bug#34688: 26.1; Crash on Pasting from Windows clipboard Patrick Brennan
2019-02-28 19:49 ` Eli Zaretskii
2019-04-01 19:15 ` Noam Postavsky
2019-04-01 19:27 ` Eli Zaretskii
2019-04-01 19:32 ` Patrick Brennan
2019-04-02 2:26 ` Eli Zaretskii
2019-04-02 3:45 ` Patrick Brennan [this message]
2019-04-02 14:49 ` Eli Zaretskii
2019-04-02 14:52 ` Patrick Brennan
2019-04-02 15:20 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAB5xGOHq_cGd4=W-jRExEt5y_aCwmVEugermt-A5G-nr48c8Ew@mail.gmail.com' \
--to=pbrennan@gmail.com \
--cc=34688@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=npostavs@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.