Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: [PATCH] (gnus-html-prefetch-images): Use `url-retrieve' rather than curl
Date: Mon, 20 Sep 2010 09:50:36 -0500	[thread overview]
Message-ID: <87wrqgh3k3.fsf@lifelogs.com> (raw)
In-Reply-To: <8739t553rp.fsf@marauder.physik.uni-ulm.de>

On Mon, 20 Sep 2010 08:26:50 +0200 Reiner Steib <reinersteib+gmane@imap.cc> wrote: 

RS> On Mon, Sep 20 2010, Katsumi Yamaoka wrote:
>> Julien Danjou <julien@danjou.info> wrote:
>>> +2010-09-19  Julien Danjou  <julien@danjou.info>
>>> +
>>> +	* gnus-html.el (gnus-html-prefetch-images): Use `url-retrieve' rather
>>> +	than curl.
>> 
>> I'm ok but I think we'd better declare we drop Emacs 21.  Otherwise
>> we have to offer a substitute for `url-retrieve' for Emacs 21 users.

RS> We may as well say that new stuff like gnus-html.el is not supported
RS> on Emacs < 22.  (BTW, it also does not work on XEmacs 21.5 beta:
RS> http://thread.gmane.org/87lj6ylqvl.fsf%40topper.koldfront.dk)

This should definitely be in etc/NEWS and we should publicize it well
for the next Gnus release.  So the supported list will be:

Emacs 22 and above
XEmacs 21.4.22
XEmacs 21.5-b29
SXEmacs

I am a little worried that Katsumi Yamaoka is the only one fixing XEmacs
problems.

Ted




  reply	other threads:[~2010-09-20 14:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-19  7:23 Julien Danjou
2010-09-19  7:27 ` Julien Danjou
2010-09-20  4:25   ` Katsumi Yamaoka
2010-09-20  6:22     ` Adam Sjøgren
2010-09-20  8:20       ` Frank Schmitt
2010-09-20 15:43         ` Adam Sjøgren
2010-09-20  6:26     ` [PATCH] " Reiner Steib
2010-09-20 14:50       ` Ted Zlatanov [this message]
2010-09-20 15:42         ` Adam Sjøgren
2010-09-20 15:56         ` [PATCH] " Lars Magne Ingebrigtsen
2010-09-20  8:10     ` Lars Magne Ingebrigtsen
2010-09-20 10:22       ` Katsumi Yamaoka
2010-09-20 10:28         ` Lars Magne Ingebrigtsen

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=87wrqgh3k3.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).