From: Tino Calancha <tino.calancha@gmail.com>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Issue with font rendering caused by one of the commits in last 48 hrs #master
Date: Sat, 21 Jan 2017 20:08:12 +0900 (JST) [thread overview]
Message-ID: <alpine.DEB.2.20.1701212005500.10479@calancha-pc> (raw)
In-Reply-To: <CAFyQvY3AaAjnAkXzHvgYBxQs5XJzSS+grMnTAzi1ej8HYuzB-w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 932 bytes --]
On Sat, 21 Jan 2017, Kaushal Modi wrote:
> Hello all,
> I keep my emacs build updated from the master branch pretty regularly.
>
> My last build was using this
> build: http://git.savannah.gnu.org/cgit/emacs.git/commit/?id=8c0fcaf66733f0538a3f024f383cb34a3c93d73c and that was good.
>
> A while back, I built using http://git.savannah.gnu.org/cgit/emacs.git/commit/?id=e5e42cefd7f2eb47d2c8660a7a317e8b08d36a82 and
> that has font issues.. whether launching emacs directly or emacsclient.
>
> So one of these 4 commits has caused the issue:
>
> e5e42cefd7 * origin/master origin/HEAD master diff-hunk-kill independent of point inside headers
> 1508b538fd * ; Revert "Improve diff-mode navigation/manipulation"
> 82a5e4dc88 * Fix free var FOO-mode-{syntax,abbrev}-table warnings
> 9c4e3097b5 * Check that variable lists are actually lists
I don't see this issue in my box.
Is it feasible for you to perform a git bisect?
next prev parent reply other threads:[~2017-01-21 11:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-21 5:45 Issue with font rendering caused by one of the commits in last 48 hrs #master Kaushal Modi
2017-01-21 11:08 ` Tino Calancha [this message]
2017-01-21 12:24 ` Eli Zaretskii
2017-01-21 14:02 ` Noam Postavsky
[not found] ` <CAFyQvY096uosF01cyXgTKGMksE1XXk-ec7SS44gHnAHJmxnaSw@mail.gmail.com>
2017-01-21 17:43 ` Kaushal Modi
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=alpine.DEB.2.20.1701212005500.10479@calancha-pc \
--to=tino.calancha@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=kaushal.modi@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.