unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
Cc: emacs-unicode@gnu.org, d.love@dl.ac.uk, emacs-bidi@gnu.org,
	emacs-devel@gnu.org
Subject: Re: synchronizing emacs-unicode branch to HEAD
Date: Tue, 9 Sep 2003 16:32:29 -0400	[thread overview]
Message-ID: <20030909203229.GA28335@fencepost> (raw)
In-Reply-To: <200309082332.IAA27881@etlken.m17n.org>

On Tue, Sep 09, 2003 at 08:32:34AM +0900, Kenichi Handa wrote:
> I hope this branch can be merged into HEAD before the HEAD
> branch is changed drastically.

I'm wondering about the opposite question: should I worry about the unicode
merge, with respect to my own branches?  How pervasive are the changes
(fairly concentrated into certain areas, or affecting every nook-and-cranny
of emacs)?

When I get the time I'll probably import the new unicode branch into arch
and check it out for myself ... actually I suppose you probably merged from
HEAD too early to get my arch-tagging changes; would you mind if I make that
same change to your CVS unicode branch?

Thanks,

-Miles
-- 
We are all lying in the gutter, but some of us are looking at the stars.
-Oscar Wilde

  parent reply	other threads:[~2003-09-09 20:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-08 23:32 synchronizing emacs-unicode branch to HEAD Kenichi Handa
2003-09-09  9:59 ` Andreas Schwab
2003-09-09 12:12   ` Kenichi Handa
2003-09-09 12:44     ` Andreas Schwab
2003-09-16  2:27       ` Kenichi Handa
2003-09-09 19:04     ` Dave Love
2003-09-09 19:02   ` Dave Love
2003-09-09 19:51     ` Andreas Schwab
2003-09-09 20:32 ` Miles Bader [this message]
2003-09-10  1:15   ` Kenichi Handa
2003-09-10  2:25     ` Miles Bader
2003-09-11  9:21 ` Dave Love
2003-09-11 18:28 ` Eli Zaretskii

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=20030909203229.GA28335@fencepost \
    --to=miles@gnu.org \
    --cc=d.love@dl.ac.uk \
    --cc=emacs-bidi@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-unicode@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).