From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Cc: emacs-devel@gnu.org
Subject: Re: bzr for Gnus
Date: Wed, 12 Aug 2009 10:09:47 -0500 [thread overview]
Message-ID: <873a7xkr0k.fsf@lifelogs.com> (raw)
In-Reply-To: 6283.1250085036@rawbw.com
On Wed, 12 Aug 2009 06:50:36 -0700 Mike Kupfer <mike.kupfer@xemacs.org> wrote:
>>>>>> "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.
MK> Hmm, I'll have to think about this. I'm reluctant to put the
MK> XEmacs-specific code off in a separate place. I suspect it would make
MK> it too easy for someone to change the common code and forget to make any
MK> corresponding changes in the XEmacs-specific code. Using nested repos
MK> might make that less of a concern, depending on the specifics of the
MK> tool and how the workflow is set up.
According to http://bazaar-vcs.org/BzrForeignBranches/Subversion
it may have to wait for the 'by-reference' work to be complete.
Meanwhile we can certainly set up something manual or automatic (a
MilesBot, if you will) to synchronize the Gnus CVS repo with the Emacs
bzr repo. As Stephen said, this may be months to 1+ years away.
Ted
next prev parent reply other threads:[~2009-08-12 15:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-08 16:24 Switching to bzr: what Emacs developers should know? Bastien
2009-08-08 18:51 ` B Smith-Mannschott
2009-08-08 19:54 ` Stefan Monnier
2009-08-08 22:41 ` Bastien
2009-08-09 1:23 ` Stefan Monnier
2009-08-11 5:42 ` Karl Fogel
2009-08-11 5:49 ` Karl Fogel
2009-08-11 17:17 ` Stefan Monnier
[not found] ` <87fxbyb3s5.fsf@notengoamigos.org>
2009-08-13 16:21 ` Stefan Monnier
2009-08-11 18:56 ` bzr for Gnus (was: Switching to bzr: what Emacs developers should know?) Ted Zlatanov
2009-08-12 5:28 ` Stephen J. Turnbull
2009-08-12 13:50 ` Mike Kupfer
2009-08-12 15:09 ` Ted Zlatanov [this message]
2009-09-08 16:27 ` bzr for Gnus Karl Fogel
2009-09-09 3:11 ` Stefan Monnier
2009-08-12 8:01 ` Miles Bader
2009-08-13 16:38 ` Stefan Monnier
2009-08-08 22:40 ` Switching to bzr: what Emacs developers should know? Bastien
2009-08-09 0:03 ` Bastien
2009-08-09 2:24 ` Óscar Fuentes
2009-08-18 9:31 ` Bastien
2009-08-09 12:42 ` CHENG Gao
2009-08-11 5:44 ` Karl Fogel
[not found] ` <8763cua0za.fsf@notengoamigos.org>
2009-08-11 15:19 ` Karl Fogel
[not found] ` <87ocqmb587.fsf@notengoamigos.org>
2009-08-11 18:20 ` Karl Fogel
[not found] ` <87bpmmb27v.fsf@notengoamigos.org>
2009-08-11 19:15 ` Karl Fogel
2009-08-12 5:50 ` CHENG Gao
2009-08-13 16:31 ` 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
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=873a7xkr0k.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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 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).