From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Abrahams Newsgroups: gmane.emacs.devel Subject: Re: Emacs antialiasing in X Date: Mon, 16 Jan 2006 08:32:21 -0500 Message-ID: <8764oke1sq.fsf@boost-consulting.com> References: <877j9ya8tu.fsf@boost-consulting.com> <200512220938.jBM9c8Lf021116@coolsville.localdomain> <873bjtoy1i.fsf@boost-consulting.com> <0B2B9218-7271-493B-A60D-F912E09E6E27@swipnet.se> <8764onlsq4.fsf@boost-consulting.com> <87oe2eisl2.fsf@boost-consulting.com> <87irsmkuzh.fsf@emfox.3322.org> <43CA0874.9090706@swipnet.se> <87k6d0exev.fsf@boost-consulting.com> <87fynoeuyg.fsf@boost-consulting.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1137428047 20838 80.91.229.2 (16 Jan 2006 16:14:07 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 16 Jan 2006 16:14:07 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 16 17:14:01 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EyWyq-00036M-PN for ged-emacs-devel@m.gmane.org; Mon, 16 Jan 2006 17:13:17 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EyWXH-0004lL-FK for ged-emacs-devel@m.gmane.org; Mon, 16 Jan 2006 10:44:47 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EyUgN-0003rG-8r for emacs-devel@gnu.org; Mon, 16 Jan 2006 08:46:03 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EyUbF-0003FF-IL for emacs-devel@gnu.org; Mon, 16 Jan 2006 08:40:48 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EyUWF-0002Q7-Ng for emacs-devel@gnu.org; Mon, 16 Jan 2006 08:35:35 -0500 Original-Received: from [207.172.4.62] (helo=smtp02.mrf.mail.rcn.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1EyUZl-0002pG-GK for emacs-devel@gnu.org; Mon, 16 Jan 2006 08:39:13 -0500 Original-Received: from 209-150-60-201.c3-0.smr-ubr2.sbo-smr.ma.cable.rcn.com (HELO localhost.localdomain.boost-consulting.com) ([209.150.60.201]) by smtp02.mrf.mail.rcn.net with ESMTP; 16 Jan 2006 08:33:12 -0500 X-IronPort-AV: i="3.99,371,1131339600"; d="scan'208"; a="195467924:sNHT27113868" Original-To: Kenichi Handa In-Reply-To: (Kenichi Handa's message of "Mon, 16 Jan 2006 13:07:54 +0900") User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (gnu/linux) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:49170 Archived-At: Kenichi Handa writes: > In article <87fynoeuyg.fsf@boost-consulting.com>, David Abrahams writes: > >> If nobody merges the plain-old "ChangeLog" files from the current XFT >> branch into what I'm doing, and my branch is used in lieu of the >> current XFT branch everything people have done in those files (in some >> cases this amounts substantial work) will be lost. If nobody cares, I >> can start new files and drop the old ones on the floor. > >> Are you telling me that edits made to ChangeLog, NEWS, etc., in the >> XFT branch are expendable? > > No. I don't know what is done in XFT branch nor how widely > ChangeLog, etc. are modified. I've never touched it. > Please discuss with XFT branch maintainers about what to do > with the current modification. > > I've just shown you how emacs-unicode-2 branch is maintained > to avoid confliction on future merging, and thought that you > can use the same method. Thanks. > Please note also that all changes to the main trunk are > periodically (once a week or so) applied also to > emacs-unicode-2 branch by Miles. Does somebody maintain a branchpoint tag that indicates the latest trunk revisions that have been merged into the branch? -- Dave Abrahams Boost Consulting www.boost-consulting.com