all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: Display scaling?
Date: Thu, 27 Jan 2022 13:22:26 +0200	[thread overview]
Message-ID: <83v8y5e83x.fsf@gnu.org> (raw)
In-Reply-To: <87r18tjv1o.fsf@yahoo.com> (message from Po Lu on Thu, 27 Jan 2022 19:08:03 +0800)

> From: Po Lu <luangruo@yahoo.com>
> Cc: emacs-devel@gnu.org
> Date: Thu, 27 Jan 2022 19:08:03 +0800
> 
> I'm fine with that too, but I intend to have this behaviour completely
> opt-in anyway, so perhaps that isn't entirely necessary.

I'd prefer not to have on master code that we are not sure will be
kept.

> BTW, is it okay for me to create a feature branch on master, or does
> someone else have to do it?

You can do it yourself (and the branch is not "on master", it is just
another branch, a sibling of the master branch).



  reply	other threads:[~2022-01-27 11:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <877danm1ds.fsf.ref@yahoo.com>
2022-01-26  6:55 ` Display scaling? Po Lu
2022-01-26  8:38   ` Eric S Fraga
2022-01-26 12:57   ` Eli Zaretskii
2022-01-26 13:17     ` Po Lu
2022-01-26 13:33       ` Eli Zaretskii
2022-01-26 13:36         ` Po Lu
2022-01-26 14:50           ` Eli Zaretskii
2022-01-27  0:57             ` Po Lu
2022-01-27  6:29               ` Eli Zaretskii
2022-01-27  6:42                 ` Po Lu
2022-01-27 10:51                   ` Po Lu
2022-01-27 11:02                     ` Eli Zaretskii
2022-01-27 11:08                       ` Po Lu
2022-01-27 11:22                         ` Eli Zaretskii [this message]
2022-01-27 11:35                           ` Po Lu
2022-01-26 13:16   ` Lars Ingebrigtsen
2022-01-26 13:37     ` Po Lu
2022-01-31 15:13   ` Dmitry Gutov
2022-02-01  1:05     ` Po Lu

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=83v8y5e83x.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.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.