From: Robert Pluim <rpluim@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: ari.roponen@gmail.com, 33442@debbugs.gnu.org
Subject: bug#33442: 26.1.90; Cairo side-by-side windows scrolling fix should be cherry-picked
Date: Sun, 09 Dec 2018 23:08:06 +0100 [thread overview]
Message-ID: <m2pnuaz73t.fsf@gmail.com> (raw)
In-Reply-To: <4270dd08-7cce-57e8-db14-eb67c5b27275@yandex.ru> (Dmitry Gutov's message of "Sat, 8 Dec 2018 16:45:01 +0200")
Dmitry Gutov <dgutov@yandex.ru> writes:
> On 08.12.2018 16:24, Eli Zaretskii wrote:
>
>> And never worked before since the code
>> was written.
>
> If that is true, I have no strong arguments for why it "has to" be on
> emacs-26.
>
>> I was asking why it has to be on emacs-26, and hoped for
>> responses that take the pros and cons into consideration and show how
>> the pros win over cons.
>
> But I'm not seeing any cons either. It's not like there are any
> plausible Cairo build users that are fine with the current state of
> emacs-26 but would get annoyed by any possible regression that the
> patch in question might introduce.
>
> Anyway, it seems I've already made all the applicable arguments at the
> beginning of this discussion. So I'll stop here.
I thought we were in a state on emacs-26 where we can get away with
cherry-picking minor fixes like the side-by-side stuff, precisely
because cairo is disabled by default. Also if any brave soul does
turn it on on emacs-26, we should probably strive to have fixed things
for them that are easy to fix.
On a separate note, should we turn cairo on by default in master? It
will still only get compiled for people who have the appropriate
development packages installed.
Robert
next prev parent reply other threads:[~2018-12-09 22:08 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 8:15 bug#33442: 26.1.90; Cairo side-by-side windows scrolling fix should be cherry-picked Ari Roponen
2018-11-20 15:58 ` Eli Zaretskii
2018-11-20 16:16 ` Dmitry Gutov
2018-11-20 17:14 ` Eli Zaretskii
2018-11-21 7:11 ` Ari Roponen
2018-11-21 21:40 ` Dmitry Gutov
2018-11-22 6:44 ` Ari Roponen
2018-11-22 12:03 ` Dmitry Gutov
2018-11-22 12:19 ` Ari Roponen
2018-11-22 14:05 ` Dmitry Gutov
2018-11-22 14:52 ` Eli Zaretskii
2018-11-22 15:22 ` Dmitry Gutov
2018-11-29 13:59 ` Dmitry Gutov
2018-11-29 12:15 ` Ari Roponen
2018-11-29 13:19 ` Robert Pluim
2018-11-29 14:06 ` Eli Zaretskii
2018-11-30 12:31 ` Ari Roponen
2018-12-08 9:55 ` Eli Zaretskii
2018-12-08 10:42 ` Dmitry Gutov
2018-12-08 11:15 ` Eli Zaretskii
2018-12-08 13:03 ` Dmitry Gutov
2018-12-08 14:24 ` Eli Zaretskii
2018-12-08 14:45 ` Dmitry Gutov
2018-12-09 22:08 ` Robert Pluim [this message]
2018-12-10 6:20 ` Eli Zaretskii
2018-12-10 13:23 ` Robert Pluim
2018-12-11 2:33 ` Dmitry Gutov
2018-12-11 3:37 ` Dmitry Gutov
2018-12-11 6:31 ` Eli Zaretskii
2018-12-11 6:27 ` Eli Zaretskii
2018-11-29 14:07 ` Dmitry Gutov
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=m2pnuaz73t.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=33442@debbugs.gnu.org \
--cc=ari.roponen@gmail.com \
--cc=dgutov@yandex.ru \
/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).