From: Kenichi Handa <handa@ni.aist.go.jp>
To: "Miles Bader" <miles@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: unicode merging
Date: Wed, 30 Jan 2008 20:04:30 +0900 [thread overview]
Message-ID: <E1JKAk2-0004U7-El@etlken.m17n.org> (raw)
In-Reply-To: <fc339e4a0801292349h70b51107lb87ed347f969e89c@mail.gmail.com> (miles@gnu.org)
In article <fc339e4a0801292349h70b51107lb87ed347f969e89c@mail.gmail.com>, "Miles Bader" <miles@gnu.org> writes:
> I'm going to merge the unicode branch into the trunk as soon as some
> conflicts are resolved.
> If you were thinking about making some big or invasive changes on the
> trunk very soon, please don't, take a break until after things are
> safely merged.
And, it is better to suspend any changes to emacs-unicode-2
branch too.
---
Kenichi Handa
handa@ni.aist.go.jp
prev parent reply other threads:[~2008-01-30 11:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 7:49 unicode merging Miles Bader
2008-01-30 11:04 ` Kenichi Handa [this message]
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=E1JKAk2-0004U7-El@etlken.m17n.org \
--to=handa@ni.aist.go.jp \
--cc=emacs-devel@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).