From: Sven Joachim <svenjoac@gmx.de>
To: Glenn Morris <rgm@gnu.org>
Cc: Juanma Barranquero <lekktu@gmail.com>,
Emacs Devel <emacs-devel@gnu.org>,
Roland Winkler <Roland.Winkler@physik.uni-erlangen.de>
Subject: Re: [Emacs-diffs] Changes to emacs/lisp/ChangeLog,v
Date: Tue, 15 Apr 2008 09:14:38 +0200 [thread overview]
Message-ID: <87hce3zj1d.fsf@gmx.de> (raw)
In-Reply-To: <sgk5izvpwh.fsf@fencepost.gnu.org> (Glenn Morris's message of "Mon, 14 Apr 2008 21:59:58 -0400")
On 2008-04-15 03:59 +0200, Glenn Morris wrote:
> "Roland Winkler" wrote:
>
>> Strange. I believe that lately I haven't changed anything in my
>> setup that could be related to this behavior. (But I upgraded from
>> GNU Emacs 22.1 to 22.2.) I'll look into that!
>
> I'm not sure, but perhaps it's using Emacs 22 to edit Emacs 23
> ChangeLogs that messes things up:
>
> http://lists.gnu.org/archive/html/emacs-devel/2008-03/msg02628.html
No, that was the other way around: editing Emacs 22 ChangeLogs with
Emacs 23 was problematic. The Emacs 23 ChangeLogs are utf-8, have a
proper coding tag and can be edited with Emacs 22 just fine. I don't
know what Roland did to mess this up.
Sven
next prev parent reply other threads:[~2008-04-15 7:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1JlDbz-00011M-B4@cvs.savannah.gnu.org>
2008-04-14 2:03 ` [Emacs-diffs] Changes to emacs/lisp/ChangeLog,v Juanma Barranquero
2008-04-14 13:17 ` Roland Winkler
2008-04-15 1:59 ` Glenn Morris
2008-04-15 7:14 ` Sven Joachim [this message]
2008-04-15 15:12 ` Roland Winkler
2008-04-15 15:16 ` Juanma Barranquero
2008-04-15 15:28 ` Roland Winkler
[not found] <E1IviQa-0007dS-Dn@localhost.localdomain>
2007-11-24 0:26 ` Juanma Barranquero
2007-11-24 15:07 ` David Kastrup
[not found] <E1HSlRs-0003n7-UH@savannah.gnu.org>
2007-03-18 4:32 ` Juanma Barranquero
2007-03-18 4:57 ` Nick Roberts
2007-03-18 5:01 ` Juanma Barranquero
2007-03-18 9:42 ` Andreas Schwab
2007-03-18 14:10 ` Juanma Barranquero
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=87hce3zj1d.fsf@gmx.de \
--to=svenjoac@gmx.de \
--cc=Roland.Winkler@physik.uni-erlangen.de \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=rgm@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 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.