[ Just joined this list, sorry if I break the thread, I don't have the
right message-ids]
Just to try and clear things up:
- The GNUstep port does not stand in the way of the merge.
- Actually even a functional Mac OS X port doesn't stand in the
way either.
- What does stand in the way is cleaning up the code by examing all the
platform-independent code modified by Emacs.app, deciding whether it
is specific to the NS code, and based on that either clean up the code
so that it works for all platforms, or move it into the ns-specific
code.
Some of those things have already been analyzed and placed into
emacs.app/nextstep/FOR_RELEASE. Actually, I'm going to split it into
FOR_RELEASE and FOR_MERGE (unless someone does it before me).
- The Emacs.app code is wanted for Emacs-23.
- The Emacs-23 feature freeze is planned for the end of June.
So we'd like to merge the code by the end of this month.
Anybody who wants to help should take a look at the FOR_MERGE file (or
FOR_RELEASE if you check it before I get to it). There are some really
easy tasks there, such as adjusting to the coding-convention.
Stefan
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Emacs-app-dev- mailing list
Emacs-app-dev-@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emacs-app-dev-
