From: Filipe Silva <filipe.silva@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Emacs 25.1.1 coredumps if company-mode pops up in a magit commit buffer window
Date: Sat, 11 Mar 2017 17:27:28 -0300 [thread overview]
Message-ID: <CAEwkUWO=q2C1EHtttWD3M13Tt0N96OPiKBcMyWx75Z=_QqnZ7Q@mail.gmail.com> (raw)
In-Reply-To: <83pohnd1ml.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 877 bytes --]
Ok Eli, thanks!
On Sat, Mar 11, 2017 at 5:01 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Filipe Silva <filipe.silva@gmail.com>
> > Date: Sat, 11 Mar 2017 16:35:02 -0300
> > Cc: Emacs developers <emacs-devel@gnu.org>
> >
> > > Sorry, it's too late for emacs-25 to get such changes. I would
> > > instead suggest that the developers of vim-empty-lines-mode modify the
> > > offending code to not hit on this problem.
> >
> > Really Eli? I've just cherry-picked your commit into emacs-25 branch
> and it's working wonderfully. I'm happy
> > to mantain my own local branch, but just curious about the rationale.
>
> The rationale is that emacs-25 is the release branch which gets only
> very safe and urgent code changes, and changes in documentation. We
> could revisit this when/if release of Emacs 25.3 from that branch is
> being considered.
>
[-- Attachment #2: Type: text/html, Size: 1435 bytes --]
prev parent reply other threads:[~2017-03-11 20:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 21:06 Emacs 25.1.1 coredumps if company-mode pops up in a magit commit buffer window Filipe Silva
2017-03-09 16:14 ` Eli Zaretskii
2017-03-09 21:12 ` Filipe Silva
2017-03-10 7:09 ` Eli Zaretskii
2017-03-10 13:16 ` Filipe Silva
2017-03-10 13:37 ` Eli Zaretskii
2017-03-11 8:33 ` Eli Zaretskii
2017-03-11 19:07 ` Filipe Silva
2017-03-11 19:27 ` Eli Zaretskii
2017-03-11 19:35 ` Filipe Silva
2017-03-11 20:01 ` Eli Zaretskii
2017-03-11 20:27 ` Filipe Silva [this message]
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='CAEwkUWO=q2C1EHtttWD3M13Tt0N96OPiKBcMyWx75Z=_QqnZ7Q@mail.gmail.com' \
--to=filipe.silva@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-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.
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.