From: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs antialiasing in X
Date: Mon, 16 Jan 2006 11:35:03 +0900 [thread overview]
Message-ID: <E1EyKD1-0007jt-00@etlken> (raw)
In-Reply-To: <87k6d0exev.fsf@boost-consulting.com> (message from David Abrahams on Sun, 15 Jan 2006 21:09:28 -0500)
In article <87k6d0exev.fsf@boost-consulting.com>, David Abrahams <dave@boost-consulting.com> writes:
>> In emacs-unicode-2, I'm using README.unicode and
>> ChangeLog.unicode. NEWS etc. are not yet written.
> I appreciate that you're trying to help (really!) but I don't
> understand what you're telling me yet. I'm concerned because there
> are merge conflicts in the plain "ChangeLog," etc., files. If I am
> going to merge the branches I have to resolve those, don't I?
I thought you are going to make a new branch, say
emacs-unicode-2-xft from the current emacs-unicode-2. Then,
what I suggest is to use something like ChangeLog.xft for
the changes you are going to made on that new branch.
In the future, emacs-unicode-2-xft branch will be merged
into emacs-unicode-2, and then emacs-unicode-2 branch will
be merged into the main trunk. Or, we may merge
emacs-unicode-2 to the main trunk at first, create a new
branch emacs-xft from there, merge emacs-unicode-2-xft into
emacs-xft, and when emacs-xft gets stable enough, merge it
into the main trunk.
On those merging, there should be no conflict in ChangeLog
if we are using different file names. And after the merge,
we can insert ChangeLog.unicode and ChangeLog.xft in
ChangeLog.
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2006-01-16 2:35 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 14:34 Emacs antialiasing in X Bill Atkins
2005-08-09 14:35 ` Jan D.
2005-12-20 20:17 ` David Abrahams
2005-12-21 5:30 ` Richard M. Stallman
2005-12-21 13:17 ` David Abrahams
2005-12-22 9:38 ` Jan D.
2006-01-12 22:56 ` David Abrahams
2006-01-13 8:49 ` Jan D.
2006-01-13 21:32 ` David Abrahams
2006-01-14 18:15 ` David Abrahams
2006-01-15 3:53 ` Emfox Zhou
2006-01-15 8:31 ` Jan Djärv
2006-01-15 16:13 ` David Abrahams
2006-01-16 0:58 ` Kenichi Handa
2006-01-16 2:09 ` David Abrahams
2006-01-16 2:35 ` Kenichi Handa [this message]
2006-01-16 3:02 ` David Abrahams
2006-01-16 4:07 ` Kenichi Handa
2006-01-16 13:32 ` David Abrahams
2006-01-16 23:45 ` Lőrentey Károly
2006-01-16 8:14 ` Jan D.
2006-01-16 9:45 ` Miles Bader
2006-01-16 13:38 ` David Abrahams
2006-01-16 13:53 ` Jan D.
2006-01-16 16:31 ` David Abrahams
2006-01-16 19:04 ` Jan D.
2006-01-16 20:17 ` David Abrahams
2006-01-16 22:48 ` Miles Bader
2006-01-17 8:34 ` Jan D.
2006-01-17 15:20 ` David Abrahams
2006-01-18 0:41 ` Miles Bader
2006-01-20 1:51 ` David Abrahams
2006-01-28 13:23 ` David Abrahams
2006-01-17 15:19 ` David Abrahams
2006-01-16 16:51 ` Stefan Monnier
2006-01-16 18:01 ` David Abrahams
2006-01-16 15:57 ` Emfox Zhou
2006-01-16 4:28 ` Stefan Monnier
2006-01-16 13:32 ` David Abrahams
2006-01-16 8:52 ` YAMAMOTO Mitsuharu
2006-01-15 8:28 ` Jan Djärv
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=E1EyKD1-0007jt-00@etlken \
--to=handa@m17n.org \
--cc=emacs-devel@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 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.