From: Miles Bader <miles@lsi.nec.co.jp>
Cc: emacs-unicode@gnu.org, emacs-devel@gnu.org
Subject: Re: Unicode branch version updates
Date: Mon, 14 Feb 2005 11:46:32 +0900 [thread overview]
Message-ID: <buod5v32707.fsf@mctpc71.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <200502140226.LAA29700@etlken.m17n.org> (Kenichi Handa's message of "Mon, 14 Feb 2005 11:26:33 +0900 (JST)")
Kenichi Handa <handa@m17n.org> writes:
>> I'd like to commit the following patch to the Emacs unicode branch.
>> It changes unicode-branch version references from "22" to "23", and
>> renames the unicode-branch-specific ChangeLog files to
>> "ChangeLog.unicode" (from "ChangeLog.22").
>
> Thank you for taking care of this matter. But, I vaguely remember
> that the reason I changed ChangeLog.unicode (I was using it when I was
> working on it locally) to ChangeLog.22 was that if the extention of
> ChangeLog file is not digits, something wrong happened. I'm not sure
> now.
>
> Could you please commit the changes after you confirm that your or
> Dave's method for automatically selecting a correct ChangeLog file
> name still works?
I use such "non-numeric ChangeLog extensions" -- e.g., in my example
code you quoted, "ChangeLog.tiling" -- regularly for my other branches
with no obvious problems.
If there is a subtle bug I haven't noticed with such ChangeLogs, we
should fix that bug. The fact that you originally used the ".unicode"
extension originally confirms that it's at least the "natural" name. :-)
Anyway, I'll do one more brief test with "unicode" in particular and
then commit it.
Thanks,
-Miles
--
Occam's razor split hairs so well, I bought the whole argument!
next prev parent reply other threads:[~2005-02-14 2:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-13 2:51 Unicode branch version updates Miles Bader
2005-02-14 2:26 ` Kenichi Handa
2005-02-14 2:46 ` Miles Bader [this message]
2005-02-14 3:40 ` Miles Bader
2005-02-14 16:02 ` Oliver Scholz
2005-02-14 17:02 ` Stefan Monnier
2005-02-14 20:21 ` Andreas Schwab
2005-02-14 20:33 ` Eli Zaretskii
2005-02-14 20:31 ` 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=buod5v32707.fsf@mctpc71.ucom.lsi.nec.co.jp \
--to=miles@lsi.nec.co.jp \
--cc=emacs-devel@gnu.org \
--cc=emacs-unicode@gnu.org \
--cc=miles@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).