all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: tgbugs@gmail.com, emacs-devel@gnu.org
Subject: Re: [PATCH] * etc/NEWS: Announce addition of BOM to utf-8-auto
Date: Mon, 30 Jan 2023 19:12:46 +0200	[thread overview]
Message-ID: <83ilgo3q0h.fsf@gnu.org> (raw)
In-Reply-To: <jwvv8ko83t8.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Mon, 30 Jan 2023 10:06:21 -0500)

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Tom Gillespie <tgbugs@gmail.com>,  emacs-devel@gnu.org
> Date: Mon, 30 Jan 2023 10:06:21 -0500
> 
> > I think both of these are mistakes of the kind I described.  I filed
> > an issue with emacs-async, but someone should probably fix the one we
> > have in ELPA.  Stefan?
> 
> It should use `emacs-internal` or `utf-8-emacs-unix` or some such very
> precisely defined format since both ends are under its control, indeed.

Probably.

> As for "the one we have in ELPA" it's auto-synchronized with the one
> upstream, so we'll get the fix when it gets installed there (and
> installing it locally would break the auto-sync'ing, causing a lot of pain).

Assuming it is maintained actively enough, yes.



  reply	other threads:[~2023-01-30 17:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-29 17:58 [PATCH] * etc/NEWS: Announce addition of BOM to utf-8-auto Tom Gillespie
2023-01-29 18:14 ` Andreas Schwab
2023-01-29 18:29 ` Eli Zaretskii
2023-01-29 19:11   ` Tom Gillespie
2023-01-29 19:38     ` Eli Zaretskii
2023-01-29 19:56       ` Tom Gillespie
2023-01-30 14:16         ` Eli Zaretskii
2023-01-30 15:06           ` Stefan Monnier
2023-01-30 17:12             ` Eli Zaretskii [this message]
2023-02-02 10:36         ` Eli Zaretskii
2023-02-02 17:56           ` Tom Gillespie

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=83ilgo3q0h.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=tgbugs@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.