From: Mike Kupfer <mike.kupfer@xemacs.org>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: Ted Zlatanov <tzz@lifelogs.com>, emacs-devel@gnu.org, ding@gnus.org
Subject: Re: bzr for Gnus (was: Switching to bzr: what Emacs developers should know?)
Date: Wed, 12 Aug 2009 06:50:36 -0700 [thread overview]
Message-ID: <6283.1250085036@rawbw.com> (raw)
In-Reply-To: Your message of "Wed, 12 Aug 2009 14:28:44 +0900." <87zla5ob1v.fsf@uwakimon.sk.tsukuba.ac.jp>
>>>>> "ST" == Stephen J Turnbull <stephen@xemacs.org> writes:
ST> An alternative to a kludgy nest of "xmas" in Gnus in Emacs would be
ST> to maintain the XEmacs compatibility code only in XEmacs package
ST> CVS, and not have it in Gnus "upstream" at all.
Hmm, I'll have to think about this. I'm reluctant to put the
XEmacs-specific code off in a separate place. I suspect it would make
it too easy for someone to change the common code and forget to make any
corresponding changes in the XEmacs-specific code. Using nested repos
might make that less of a concern, depending on the specifics of the
tool and how the workflow is set up.
mike
next prev parent reply other threads:[~2009-08-12 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <874osi6zpe.fsf@bzg.ath.cx>
[not found] ` <28c656e20908081151h55a4b566v4cfc7c49c5ca2a37@mail.gmail.com>
[not found] ` <jwvvdky6qia.fsf-monnier+emacs@gnu.org>
[not found] ` <87ab26aoix.fsf@canonical.com>
2009-08-11 18:56 ` Ted Zlatanov
2009-08-12 5:28 ` Stephen J. Turnbull
2009-08-12 13:50 ` Mike Kupfer [this message]
2009-08-12 15:09 ` bzr for Gnus Ted Zlatanov
2009-09-08 16:27 ` Karl Fogel
2009-09-09 3:11 ` Stefan Monnier
2009-08-12 8:01 ` Miles Bader
2009-08-13 16:38 ` Stefan Monnier
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=6283.1250085036@rawbw.com \
--to=mike.kupfer@xemacs.org \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=stephen@xemacs.org \
--cc=tzz@lifelogs.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.
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 NNTP newsgroup(s).