From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Jason Rumney <jasonr@gnu.org>
Cc: Adrian Robert <Adrian.B.Robert@gmail.com>, emacs-devel@gnu.org
Subject: Re: Carbon port emacs-unicode-2 build problem under MacOSX
Date: Wed, 07 Nov 2007 11:09:50 -0500 [thread overview]
Message-ID: <jwvbqa6oxea.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <4731D43F.3060007@gnu.org> (Jason Rumney's message of "Wed, 07 Nov 2007 15:05:35 +0000")
> 3. Merge unicode-2 to the trunk (I think it is ready now, so immediately
> after 22.2 release would be good).
AFAIK the "merge" can be done right now: it's just a matter fo changing
which branch is condiered "the trunk". The only thing missing is some
agreement as to *how* to do it, the main issue being the what to put
into the ChangeLog. Richard wants the ChangeLog to be massaged in a way
similar to what was done for multi-tty, and when this came up, everybody
ran away screeming (there's about 280KB of ChangeLog entries on the
unicode branch).
Stefan
next prev parent reply other threads:[~2007-11-07 16:09 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 12:02 Carbon port emacs-unicode-2 build problem under MacOSX CHENG Gao
2007-11-06 12:14 ` CHENG Gao
2007-11-06 12:29 ` Kenichi Handa
2007-11-06 13:52 ` CHENG Gao
2007-11-06 19:28 ` Ted Zlatanov
2007-11-06 23:27 ` Glenn Morris
2007-11-07 4:59 ` Ted Zlatanov
2007-11-07 13:19 ` Carbon port vs. Emacs.app plus Emacs.app problem report w/test-case Mike Mattie
2007-11-07 13:54 ` Ted Zlatanov
2007-11-07 15:45 ` Mike Mattie
2007-11-06 12:34 ` Carbon port emacs-unicode-2 build problem under MacOSX Jason Rumney
2007-11-06 13:58 ` CHENG Gao
2007-11-06 19:26 ` Ted Zlatanov
2007-11-07 4:13 ` YAMAMOTO Mitsuharu
2007-11-07 5:24 ` Ted Zlatanov
2007-11-07 5:52 ` YAMAMOTO Mitsuharu
2007-11-07 6:03 ` YAMAMOTO Mitsuharu
2007-11-07 14:19 ` Ted Zlatanov
2007-11-07 14:34 ` Jason Rumney
[not found] ` <m2abpqt5mm.fsf@lifelogs.com>
2007-11-07 16:40 ` Adrian Robert
2007-11-08 4:42 ` Richard Stallman
2007-11-08 1:27 ` YAMAMOTO Mitsuharu
2007-11-08 2:31 ` YAMAMOTO Mitsuharu
2007-11-24 9:18 ` YAMAMOTO Mitsuharu
2008-02-12 0:59 ` YAMAMOTO Mitsuharu
2007-11-07 14:15 ` Adrian Robert
2007-11-07 15:05 ` Jason Rumney
2007-11-07 16:09 ` Stefan Monnier [this message]
2007-11-08 4:42 ` Richard Stallman
2007-11-08 15:56 ` Dan Nicolaescu
2007-11-09 4:12 ` Richard Stallman
2007-11-09 7:47 ` Dan Nicolaescu
2007-11-09 10:34 ` Eli Zaretskii
2007-11-09 15:09 ` Dan Nicolaescu
2007-11-10 17:54 ` Richard Stallman
2007-11-12 5:17 ` How to re-orgranize ChangeLog.unicode for merging Kenichi Handa
2007-11-12 20:22 ` Eli Zaretskii
2007-11-12 22:17 ` Andreas Schwab
2007-11-13 4:08 ` Eli Zaretskii
2007-11-18 22:47 ` Richard Stallman
2007-11-18 22:47 ` Richard Stallman
2007-11-07 16:14 ` Carbon port emacs-unicode-2 build problem under MacOSX Dan Nicolaescu
2007-11-08 4:42 ` Richard Stallman
2007-11-07 18:30 ` CHENG Gao
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=jwvbqa6oxea.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=Adrian.B.Robert@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jasonr@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).