From: Kenichi Handa <handa@m17n.org>
To: dhruva <dhruvakm@gmail.com>
Cc: sean.sieger@gmail.com, help-gnu-emacs@gnu.org, emacs-devel@gnu.org
Subject: Re: Bumpe unicode2 branch version to 23.0.52
Date: Tue, 04 Sep 2007 20:22:57 +0900 [thread overview]
Message-ID: <E1ISWUj-0003On-G0@etlken.m17n.org> (raw)
In-Reply-To: <e3f230850709040339m10d697b1h97226b30c9fb8d38@mail.gmail.com> (message from dhruva on Tue, 4 Sep 2007 16:09:13 +0530)
The branch tag for Unicode version of Emacs is
emacs-unicode-2. It's very unfortunate that it is not yet
merged into the trunk. I hope that Richard decides to that
soon. In this May, he said that he wanted one or two months
to decide which feature to include in Emacs 22.2 before
merging emacs-unicode-2.
Those who want to distinguish the trunk version and
emacs-unicode-2 version, please check the variable
mule-version.
The trunk: "5.0 (SAKAKI)"
emacs-unicode-2: "6.0 (HANACHIRUSATO)"
---
Kenichi Handa
handa@m17n.org
In article <e3f230850709040339m10d697b1h97226b30c9fb8d38@mail.gmail.com>, dhruva <dhruvakm@gmail.com> writes:
> Hi,
> On 9/4/07, Peter Dyballa <Peter_Dyballa@web.de> wrote:
> >
> > Am 04.09.2007 um 11:48 schrieb Sean Sieger:
> >
> > >
> > > People are confused by the version. Since trunk is 23.0.50, mtty
> > > branch
> > > is 23.0.51, I wonder if it will make more sense to bump unicode2
> > > branch
> > > to 23.0.52.
> > >
> > > Confused by the the version and the name of the branch--did the name
> > > change from emacs-unicode-2 to emacs-unicode-base?
> > >
> >
> > http://cvs.savannah.gnu.org/viewvc/emacs/emacs/?pathrev=emacs-
> > unicode-2 does not show that branch name ...
> >
> >From the web CVS front end, 'emacs-unicode-base' is a NON branch tag
> (just a simple TAG). The valid UNICODE related branch tag is
> 'emacs-unicode-2' (earlier branch was emacs-unicode). The UNICODE
> maintainer is the best person to clarify though.
> -dky
> --
> Dhruva Krishnamurthy
> Contents reflect my personal views only!
> _______________________________________________
> Emacs-devel mailing list
> Emacs-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2007-09-04 11:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3tzqbi7xy.fsf@gmail.com>
2007-09-04 7:19 ` Bumpe unicode2 branch version to 23.0.52 (was: does emacs-unicode-2 branch stop developing?) Leo
2007-09-04 9:48 ` Bumpe unicode2 branch version to 23.0.52 Sean Sieger
2007-09-04 10:30 ` Peter Dyballa
2007-09-04 10:39 ` dhruva
2007-09-04 11:22 ` Kenichi Handa [this message]
2007-09-04 22:58 ` Richard Stallman
2007-09-04 23:54 ` Glenn Morris
2007-09-05 5:49 ` David Kastrup
2007-09-05 20:02 ` Richard Stallman
2007-09-04 22:58 ` Bumpe unicode2 branch version to 23.0.52 (was: does emacs-unicode-2 branch stop developing?) Richard Stallman
2007-09-10 1:00 ` Xavier Maillard
2007-09-05 1:00 ` Xavier Maillard
2007-09-05 5:48 ` Bumpe unicode2 branch version to 23.0.52 David Kastrup
2007-09-10 1:00 ` Xavier Maillard
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=E1ISWUj-0003On-G0@etlken.m17n.org \
--to=handa@m17n.org \
--cc=dhruvakm@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=sean.sieger@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 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).