From: Miles Bader <miles@lsi.nec.co.jp>
Cc: d.love@dl.ac.uk, emacs-devel@gnu.org
Subject: Re: synchronizing emacs-unicode branch to HEAD
Date: 10 Sep 2003 11:25:54 +0900 [thread overview]
Message-ID: <buo65k1crbh.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <200309100115.KAA00628@etlken.m17n.org>
Kenichi Handa <handa@m17n.org> writes:
> So, if your change depends on macros in old charset.h and coding.h,
> you must pay big attention to the change. Otherwise, I think you
> don't have to worry about the unicode merge that much.
Cool.
> > 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?
>
> I don't mind as far as that change doesn't make future merging of
> emacs-unicode-2 into HEAD difficult.
If I make changes to the unicode branch which I've also made to HEAD,
then there will be be redundant hunks. In general I think CVS silently
ignores redundant changes (and the tagline changes are pretty well
isolated at the end of files), so this shouldn't cause any problems, but
I'm not entirely sure about the the specific case of `cvs update -j'
(which is what I presume you'll use to do the merge); does anyone know
for sure?
Thanks
-Miles
--
Next to fried food, the South has suffered most from oratory.
-- Walter Hines Page
next prev parent reply other threads:[~2003-09-10 2:25 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
2003-09-10 1:15 ` Kenichi Handa
2003-09-10 2:25 ` Miles Bader [this message]
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=buo65k1crbh.fsf@mcspd15.ucom.lsi.nec.co.jp \
--to=miles@lsi.nec.co.jp \
--cc=d.love@dl.ac.uk \
--cc=emacs-devel@gnu.org \
--cc=miles@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).