unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "T.V Raman" <raman@google.com>
Cc: ismail@i10z.com, rpluim@gmail.com, emacs-devel@gnu.org
Subject: Re: Font problem on git master
Date: Mon, 20 Jan 2020 17:50:29 +0200	[thread overview]
Message-ID: <83a76ixh2y.fsf@gnu.org> (raw)
In-Reply-To: <p91h80qkv0n.fsf@google.com> (raman@google.com)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 271 bytes --]

> From: "T.V Raman" <raman@google.com>
> Cc: 02smail D0‹2nmez <ismail@i10z.com>,
>  emacs-devel@gnu.org
> Date: Mon, 20 Jan 2020 07:27:52 -0800
> 
> Could we update the News file with  details on what font backends are
> now recommended?

Indeed, I think we should.



  reply	other threads:[~2020-01-20 15:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-20 10:20 Font problem on git master İsmail Dönmez
2020-01-20 10:39 ` Robert Pluim
2020-01-20 10:45   ` İsmail Dönmez
2020-01-20 11:00     ` Robert Pluim
2020-01-20 11:26       ` İsmail Dönmez
2020-01-20 12:38         ` Robert Pluim
2020-01-20 12:53           ` İsmail Dönmez
2020-01-20 13:52             ` Robert Pluim
2020-01-20 14:35               ` Robert Pluim
2020-01-20 15:27                 ` T.V Raman
2020-01-20 15:50                   ` Eli Zaretskii [this message]
2020-01-20 17:31                     ` Eli Zaretskii
2020-01-20 18:33                       ` Robert Pluim
2020-01-20 18:52                         ` Eli Zaretskii
2020-01-20 16:21                   ` Robert Pluim
2020-01-20 18:22                   ` T.V Raman
2020-01-20 15:47                 ` Eli Zaretskii
2020-01-20 16:34                   ` Robert Pluim
2020-01-20 17:33                     ` Eli Zaretskii
2020-01-20 18:05                 ` İsmail Dönmez
2020-01-20 19:33                 ` Andreas Schwab

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=83a76ixh2y.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=ismail@i10z.com \
    --cc=raman@google.com \
    --cc=rpluim@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 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).