Gnus development mailing list
 help / color / mirror / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Cc: ding@gnus.org
Subject: Re: Gnus cleanup
Date: Tue, 09 Feb 2016 10:30:48 -0500	[thread overview]
Message-ID: <jwvh9hhdhul.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: <87h9hied21.fsf@gnus.org>

> So I could just remove the compat function to.  But it is theoretically
> feasible that somebody out there are calling
> gnus-window-inside-pixel-edges in their own code.

What I've used in the past goes along the lines of:
- Use my gut-feeling to decide whether to keep the obsolete compat
  function, erring on the side of "removal" rather than on the "safe" side.
- Some of the removed functions may later be re-added based on
  bug-reports from user.

And sometimes it's easier to just remove them all or just keep them all.


        Stefan




  parent reply	other threads:[~2016-02-09 15:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-09  4:13 Lars Ingebrigtsen
2016-02-09  8:35 ` Michael Albinus
2016-02-09  8:35 ` Eric S Fraga
2016-02-09 11:42 ` Malcolm Purvis
2016-02-09 15:30 ` Stefan Monnier [this message]
2016-02-09 23:08   ` Lars Ingebrigtsen
2016-02-10  0:50 ` Greg Troxel
2016-02-12  4:19 ` Lars Ingebrigtsen
2016-02-13  0:22   ` Frank Haun
2016-02-13  1:57   ` Eric Abrahamsen
2016-02-13  3:17     ` Eric Abrahamsen
2016-02-13  3:43       ` Lars Ingebrigtsen
2016-02-13  4:26         ` Eric Abrahamsen
2016-02-13  4:59           ` Lars Ingebrigtsen
2016-02-13 12:00   ` Frank Haun
2016-02-13 15:37     ` Richard Stallman
2016-02-14  2:35     ` Lars Ingebrigtsen
2016-02-14  3:13       ` Adam Sjøgren
2016-02-14 13:12       ` Frank Haun
2016-02-17 21:10       ` Frank Haun
2016-02-18 12:29         ` Frank Haun
2016-03-07 13:52   ` Ted Zlatanov

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=jwvh9hhdhul.fsf-monnier+gmane.emacs.devel@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --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.
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).