From: Miles Bader <miles@gnu.org>
Cc: Miles Bader <miles@lsi.nec.co.jp>,
eliz@gnu.org, Reiner Steib <Reiner.Steib@gmx.de>,
Emacs development <emacs-devel@gnu.org>
Subject: Re: nndb.el requires tcp
Date: Fri, 10 Sep 2004 10:01:08 -0400 [thread overview]
Message-ID: <20040910140108.GA16207@fencepost> (raw)
In-Reply-To: <ilur7paclxh.fsf@latte.josefsson.org>
On Fri, Sep 10, 2004 at 03:07:06PM +0200, Simon Josefsson wrote:
> > Maybe it be better to install it only in Emacs CVS _or_ in v5-10 (Gnus
> > stable branch) and let it propagate to the other by Miles' arch
> > synching? We should do whatever is more convenient for Miles, I
> > think.
Thanks Reiner!
It's slightly easier for me if changes are installed on the Gnus v5-10
branch, from where I can propagate them to Emacs CVS.
> Right. Exactly how does this work? Is it fully automated?
No, but it's only a few simple commands for changes that don't generate any
conflicts (I probably _could_ automate it fully in that case, but I actually
like staying in the loop a bit so that I can catch any unexpected weirdness).
> Syncing V5-10 and Emacs CVS automatically seems useful, but there are some
> stuff in Gnus CVS for XEmacs compatibility that historically hasn't been
> included in the Emacs Gnus version.
I wouldn't worry about it; I think any such problems will be rare and small,
and easily enough fixed after the fact if they escape the casual checking I
do during merges.
I don't really think there's a problem with having a bit of XEmacs-specific
code in Emacs anyway if it makes maintaining Gnus much easier; again, if
something does become an issue, it can be addressed at that point.
-Miles
--
Ich bin ein Virus. Mach' mit und kopiere mich in Deine .signature.
next prev parent reply other threads:[~2004-09-10 14:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-10 10:25 nndb.el requires tcp Eli Zaretskii
2004-09-10 10:50 ` Simon Josefsson
2004-09-10 11:31 ` Eli Zaretskii
2004-09-10 11:49 ` Simon Josefsson
2004-09-10 12:38 ` Reiner Steib
2004-09-10 13:07 ` Simon Josefsson
2004-09-10 14:01 ` Miles Bader [this message]
2004-09-16 13:27 ` merge emacs Gnus changes (was: nndb.el requires tcp) Reiner Steib
2004-09-16 13:38 ` Miles Bader
2004-09-16 13:45 ` Miles Bader
2004-09-18 13:16 ` Miles Bader
2004-09-19 19:40 ` merge emacs Gnus changes Reiner Steib
2004-09-19 20:43 ` Reiner Steib
2004-09-19 21:00 ` Miles Bader
2004-09-10 14:12 ` [Gnus] @copying in {pgg,sieve}.texi; FLIM files (was: nndb.el requires tcp) Reiner Steib
2004-09-17 9:05 ` nndb.el requires tcp Kai Grossjohann
2004-09-17 13:25 ` Lars Magne Ingebrigtsen
2004-09-18 19:07 ` Richard Stallman
2004-09-18 20:13 ` Lars Magne Ingebrigtsen
2004-09-20 0:05 ` Richard Stallman
2004-09-20 7:59 ` Kai Grossjohann
2004-09-17 23:21 ` Richard Stallman
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=20040910140108.GA16207@fencepost \
--to=miles@gnu.org \
--cc=Reiner.Steib@gmx.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=miles@lsi.nec.co.jp \
/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).