all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, Ivan Shmakov <ivan@siamics.net>
Cc: 19822@debbugs.gnu.org, emacs-devel@gnu.org
Subject: bug#19822: url-retrieve: allow to fail when no document is associated with the URI
Date: Fri, 25 Dec 2015 15:47:55 -0800 (PST)	[thread overview]
Message-ID: <d14d541e-e7b8-4728-b4e5-a6f6a898094a__31138.1722953685$1451087363$gmane$org@default> (raw)
In-Reply-To: <87r3iawdyl.fsf@gnus.org>

> I think all these non-http{s,} things in the URL library should be
> marked obsolete and removed.  There is very little utility to them (some
> have been broken for years without anybody noticing), and they are very
> fiddly to maintain.
> 
> Anybody mind if I remove them for Emacs 25.2?

1. Such a proposal should explicitly list each of the "things" you
   propose to mark as obsolete.

2. Marking something as obsolete (deprecating it) does not imply
   that you can remove it.  Normally (although I do know that Emacs
   is not necessarily normal) deprecated "things" remain, and remain
   supported for quite some time before they are desupported.  And
   that means that their supporting code remains (is not removed).

   Or did you perhaps mean remove only from "the URL library",
   and not remove from Emacs?

(All of this said, I probably do not care, personally, what you
do with the unspecified "non-http{s,} things in the URL library"
that you want to remove.)





  parent reply	other threads:[~2015-12-25 23:47 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-06 19:15 bug#17959: eww: FTP is not supported; but with ftp_proxy, it is Ivan Shmakov
2014-11-04 16:40 ` Ted Zlatanov
2014-11-10 21:20 ` Lars Magne Ingebrigtsen
2014-11-19  8:04   ` Ivan Shmakov
2014-11-19 17:24     ` Lars Magne Ingebrigtsen
2014-11-19 18:37       ` debbugs.gnu.org: is it user-centric or developer-centric? Ivan Shmakov
2014-11-19 18:53         ` Glenn Morris
2014-11-19 19:27           ` Ivan Shmakov
2014-12-16 20:09     ` bug#17959: support accessing FTP services via HTTP proxies Ivan Shmakov
2015-01-12 21:40       ` Ivan Shmakov
2015-02-09 16:55         ` bug#19822: url-retrieve: allow to fail when no document is associated with the URI Ivan Shmakov
2015-12-25 19:00           ` Lars Ingebrigtsen
2015-12-25 23:47             ` Drew Adams
2015-12-25 23:47             ` Drew Adams [this message]
2015-12-25 19:00           ` Lars Ingebrigtsen
2015-12-28 22:07             ` Ted Zlatanov
2015-12-28 22:07             ` Ted Zlatanov
2015-12-28 22:30               ` Lars Ingebrigtsen
2015-12-28 22:30               ` Lars Ingebrigtsen
2019-09-30  1:03           ` Stefan Kangas
2019-09-30  5:47             ` Lars Ingebrigtsen
2019-09-30  7:21               ` Eli Zaretskii
2019-09-30  7:30                 ` Lars Ingebrigtsen
2019-09-30  8:22                   ` Eli Zaretskii
2019-09-30 14:40                     ` Lars Ingebrigtsen
2019-09-30 15:05                       ` Eli Zaretskii
2019-10-01 13:19                       ` Stefan Kangas
2019-10-01 13:37                         ` Eli Zaretskii
2019-10-01 13:44                           ` Stefan Kangas
2019-10-01 14:51                             ` Eli Zaretskii
2019-10-01 15:13                               ` Stefan Kangas
2019-10-01 15:24                                 ` Eli Zaretskii
2019-10-01 13:56                         ` Lars Ingebrigtsen
2019-10-01 14:06                           ` Stefan Kangas
2019-10-01 14:24                             ` Stefan Kangas
2019-10-01 15:13                               ` Lars Ingebrigtsen
2019-10-01 16:07                                 ` Stefan Kangas
2015-02-09 17:04         ` bug#17959: support accessing FTP services via HTTP proxies Ivan Shmakov

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='d14d541e-e7b8-4728-b4e5-a6f6a898094a__31138.1722953685$1451087363$gmane$org@default' \
    --to=drew.adams@oracle.com \
    --cc=19822@debbugs.gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=ivan@siamics.net \
    --cc=larsi@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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.