From: David Abrahams <dave@boost-consulting.com>
Cc: Miles Bader <snogglethorpe@gmail.com>
Subject: Re: Emacs antialiasing in X
Date: Thu, 19 Jan 2006 20:51:07 -0500 [thread overview]
Message-ID: <uirsfpsz8.fsf@boost-consulting.com> (raw)
In-Reply-To: fc339e4a0601171641r6d27c5cp@mail.gmail.com
Miles Bader <snogglethorpe@gmail.com> writes:
> 2006/1/18, David Abrahams <dave@boost-consulting.com>:
>> > I've attached a diff from HEAD 2006-01-12 10:24 to the XFT branch (the
>> > latest sync with head occurred then). It is not that much.
>>
>> I could easily(?) apply this patch to emacs-unicode-2 myself, but I
>> don't want to duplicate work if Miles is going to do it too. So,
>> Miles, what'll it be?
>
> My only concern is if any branch merging is done.
>
> If you want to apply this patch directly on the emacs-unicode-2
> branch, and work there, then I've no reason to be involved (I dunno
> whether that's acceptable to Kenichi et al though).
I guess I would be slightly more comfortable if someone with more
experience with the emacs codebase (like you) wanted to merge the two
branches together. It seems like a lot to ask, but you did volunteer
:). However, it sounds like it's a small thing so if you want to back
out, I can probably manage.
> If you want to work on a new branch (derived from emacs-unicode-2),
> and later merge it into emacs-unicode-2, then I'd like to be the one
> that creates the new branch (and later merges it back into
> emacs-unicode-2).
>
> So if it's the latter, give me the word, and I'll make a new
> branch.
Well, that would keep me out of everyone's hair -- if someone will
give me commit privileges, that is. Who do I ask? Otherwise I'll
have to ask somebody to keep committing my intermediate work.
> [Actually, probably the simplest thing to do is for me to make it a
> clone of emacs-unicode-2, and let you apply Jan's patch.]
Won't that make *more* work when things are integrated?
--
Dave Abrahams
Boost Consulting
www.boost-consulting.com
next prev parent reply other threads:[~2006-01-20 1:51 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
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 [this message]
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=uirsfpsz8.fsf@boost-consulting.com \
--to=dave@boost-consulting.com \
--cc=snogglethorpe@gmail.com \
/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.