From: David Abrahams <dave@boost-consulting.com>
Cc: "Jan D." <jan.h.d@swipnet.se>,
emacs-devel@gnu.org, Kenichi Handa <handa@m17n.org>,
miles@gnu.org
Subject: Re: Emacs antialiasing in X
Date: Tue, 17 Jan 2006 10:19:01 -0500 [thread overview]
Message-ID: <87lkxe9922.fsf@boost-consulting.com> (raw)
In-Reply-To: <fc339e4a0601161448q3233b50er@mail.gmail.com> (Miles Bader's message of "Tue, 17 Jan 2006 07:48:38 +0900")
Miles Bader <snogglethorpe@gmail.com> writes:
> 2006/1/17, David Abrahams <dave@boost-consulting.com>:
>> > No tag, but you can use the date specifier, the cvs log message gives
>> > the date.
>>
>> Thanks, I'll do that. FWIW, if you do use such tags you can
>> substantially reduce the number of conflicts you see upon merging.
>
> This whole conversation is making me very nervous ....
Me too. If I have to learn and install a whole new version control
system just to contribute to a project that's actually officially
stored in CVS, it raises the barrier to entry considerably.
> I also merge into the emacs-unicode-2 branch (using arch), and this is
> normally pretty easy. I'm afraid that a botched merge (all too easy
> with CVS) into that same branch will make things very painful for me.
>
> Jan, how many changes are there in the XFT branch, compared to the trunk?
>
> If it's not many, how about instead I update my XFT branch in arch
> (it's out of date because it got merged into from the trunk, which
> caused lots of problems for my syncing scripts, but I can just
> probably just recreate it from scratch), then merge that into the
> unicode branch (using arch), and make a new combined branch, and then
> make a new CVS branch from that...?
Well :)
That's certainly an attractive idea from my point of view! Please do
it; I'll be very glad not to have to worry about that step.
--
Dave Abrahams
Boost Consulting
www.boost-consulting.com
next prev parent reply other threads:[~2006-01-17 15:19 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
2006-01-28 13:23 ` David Abrahams
2006-01-17 15:19 ` David Abrahams [this message]
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
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=87lkxe9922.fsf@boost-consulting.com \
--to=dave@boost-consulting.com \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.org \
--cc=jan.h.d@swipnet.se \
--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).