unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Third <alan@idiocy.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Some NS port changes
Date: Tue, 15 Jan 2019 16:12:03 +0000	[thread overview]
Message-ID: <20190115161203.GA31959@breton.holly.idiocy.org> (raw)
In-Reply-To: <83lg3ndz4s.fsf@gnu.org>

On Mon, Jan 14, 2019 at 05:42:27PM +0200, Eli Zaretskii wrote:
> > Date: Sun, 13 Jan 2019 23:19:50 +0000
> > From: Alan Third <alan@idiocy.org>
> > 
> > I’ve not tried it myself, but it may be worth cherrypicking commit
> > 7dcce0a574a6b614961fb61c2b0936f56472f4df into emacs-26.
> 
> If this helps, it's fine with me to cherrypick that commit.

Thanks I’ve done some testing and it looks good in emacs-26, so I’ve
pushed it up.

BTW, I’ve accidentally pushed a commit with an invalid email address
to scratch/ns/next. Now that I’ve published it I know I’m not supposed
to rewrite history, but do we care too much about that on scratch
branches?
-- 
Alan Third



  reply	other threads:[~2019-01-15 16:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-13 23:19 Some NS port changes Alan Third
2019-01-14 15:42 ` Eli Zaretskii
2019-01-15 16:12   ` Alan Third [this message]
2019-01-15 16:33     ` Stefan Monnier
2019-01-15 16:58       ` Alan Third
2019-01-15 20:35 ` Charles A. Roelli
2019-01-15 22:22   ` Alan Third
2019-02-10 22:14 ` Alan Third
2019-02-11 10:59   ` Robert Pluim
2019-02-11 22:14     ` Alan Third
2019-02-12  9:21       ` Robert Pluim
2019-02-14  9:08         ` Robert Pluim
2019-02-14 18:17           ` Alan Third
2019-02-15 10:51             ` Robert Pluim
  -- strict thread matches above, loose matches on Subject: below --
2019-01-20  6:11 Zhang Haijun
2019-01-20 11:09 ` Alan Third
2019-01-20 11:20   ` Zhang Haijun
2019-01-20 12:26     ` Eli Zaretskii
2019-01-20 12:23 ` Eli Zaretskii

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=20190115161203.GA31959@breton.holly.idiocy.org \
    --to=alan@idiocy.org \
    --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 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).