From: "Juanma Barranquero" <lekktu@gmail.com>
To: "David Kastrup" <dak@gnu.org>
Cc: Andreas Schwab <schwab@suse.de>, Emacs-Devel <emacs-devel@gnu.org>
Subject: Re: Merging unicode
Date: Wed, 30 May 2007 00:37:06 +0200 [thread overview]
Message-ID: <f7ccd24b0705291537o252b207cg17c6dac2aed7fb92@mail.gmail.com> (raw)
In-Reply-To: <857iqrxpkj.fsf@lola.goethe.zz>
On 5/29/07, David Kastrup <dak@gnu.org> wrote:
> Well, that the jury is somewhat out on the multi-tty branch.
OTOH the unicode branch is ready to be merged.
> Then there is the matter of non-existing Texinfo information for the
> Elisp manual and also the Emacs manual.
Why should that affect the merge? We're not going to release 23.1 any time soon.
> Merging unicode2 first will cause synch headaches in the multitty
> branch (larger than the other way round, presumably).
I agree with Jason: the conflicts are the same, the only thing that
varies is where do they happen and who shoulders the effort.
> But on the other hand, Emacs 22.1 is in its final throws. Synching
> unicode-2 will make parallel updates of EMACS_22_BASE and trunk a bit
> more inconvenient. And maybe we just need that bit of inconvenience
> to shoo Emacs 22.1 out the door.
It's an option to ponder... :)
Juanma
--
What is this talk of "release"? Klingons do not make software
"releases". Our software "escapes" leaving a bloody trail of designers
and quality assurance people in its wake.
-- The Klingon Programmer
next prev parent reply other threads:[~2007-05-29 22:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 15:38 Merging unicode Juanma Barranquero
2007-05-29 17:38 ` Andreas Schwab
2007-05-29 19:01 ` Juanma Barranquero
2007-05-29 21:55 ` David Kastrup
2007-05-29 22:12 ` Jason Rumney
2007-05-29 22:52 ` David Kastrup
2007-05-29 22:37 ` Juanma Barranquero [this message]
2007-05-29 22:46 ` Jason Rumney
2007-05-29 22:54 ` Juanma Barranquero
2007-05-30 4:26 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f7ccd24b0705291537o252b207cg17c6dac2aed7fb92@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=schwab@suse.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.