From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: testing Gnus and Emacs/XEmacs compatibility (was: gnus-buffer-live-p?)
Date: Fri, 25 Feb 2011 11:22:28 -0600 [thread overview]
Message-ID: <8739ncav1n.fsf@lifelogs.com> (raw)
In-Reply-To: <sa362s89i6k.fsf@cigue.easter-eggs.fr>
On Fri, 25 Feb 2011 17:45:39 +0100 Julien Danjou <julien@danjou.info> wrote:
JD> What's the point of it? It seems to be very old and new code uses
JD> buffer-live-p. I think it predates an arrival of buffer-live-p in a
JD> "recent" Emacs. Can I remove it and replace it with buffer-live-p?
I don't know the answer and don't have a usable XEmacs or Emacs 23 setup
to test. But your question makes me wonder if we should have such a
thing. I've been planning for *years* to set up a build farm for the
latest Emacs trunk checkout; adding XEmacs and a few other instances
shouldn't be too hard. For Gnus specifically it would let us find out
very quickly if a checkin breaks compatibility, and we can think of a
way to do "testing" branches to test changes without putting them in the
master branch.
Ted
next prev parent reply other threads:[~2011-02-25 17:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 16:45 gnus-buffer-live-p? Julien Danjou
2011-02-25 17:22 ` Ted Zlatanov [this message]
2011-02-25 17:29 ` testing Gnus and Emacs/XEmacs compatibility Adam Sjøgren
2011-02-25 18:37 ` David Engster
2011-02-25 18:49 ` Ted Zlatanov
2011-02-25 19:04 ` David Engster
2011-02-25 19:51 ` Ted Zlatanov
2011-03-05 12:05 ` Lars Magne Ingebrigtsen
2011-03-05 14:36 ` Adam Sjøgren
2011-03-05 14:51 ` David Engster
2011-03-05 15:09 ` Adam Sjøgren
2011-03-07 1:11 ` Ted Zlatanov
2011-03-07 7:11 ` David Engster
2011-03-07 17:23 ` Ted Zlatanov
2011-03-07 17:37 ` David Engster
2011-03-07 18:07 ` Ted Zlatanov
2011-03-15 17:40 ` Lars Magne Ingebrigtsen
2011-03-15 18:22 ` Ted Zlatanov
2011-03-16 16:30 ` David Engster
2011-03-17 17:12 ` Lars Magne Ingebrigtsen
2011-03-07 19:00 ` Adam Sjøgren
2011-03-07 19:14 ` David Engster
2011-03-07 19:53 ` Adam Sjøgren
2011-03-07 20:36 ` David Engster
2011-03-07 20:41 ` Adam Sjøgren
2011-02-25 21:59 ` Julien Danjou
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=8739ncav1n.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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.
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).