From: storm@cua.dk (Kim F. Storm)
To: Juri Linkov <juri@jurta.org>
Cc: Chong Yidong <cyd@stupidchicken.com>, emacs-devel@gnu.org
Subject: Re: Online help and help-for-help improvements
Date: Mon, 03 Mar 2008 14:37:54 +0100 [thread overview]
Message-ID: <87lk50c4i5.fsf@kfs-lx.rd.rdm> (raw)
In-Reply-To: <87od9xyiz7.fsf@jurta.org> (Juri Linkov's message of "Sun\, 02 Mar 2008 04\:59\:48 +0200")
Juri Linkov <juri@jurta.org> writes:
> ISTR there was a policy to declare a function obsolete in the upcoming
> release, that gives enough time for authors to fix external packages,
> and after this release delete it in the next release.
Where do you declare it obsolete ? In a news group ?
How long before a release should you do that?
One way would be to simply add aliases for the new names
now for 22.2 release, and declare the old names obsolete
Then we can remove the old names from 23.x now.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2008-03-03 13:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 12:04 Online help and help-for-help improvements Kim F. Storm
2008-02-28 21:04 ` Juri Linkov
2008-02-28 22:49 ` Kim F. Storm
2008-02-28 23:01 ` Juri Linkov
2008-02-28 23:12 ` Kim F. Storm
2008-02-28 21:08 ` Chong Yidong
2008-02-28 23:01 ` Kim F. Storm
2008-02-28 23:48 ` Chong Yidong
2008-02-29 12:22 ` Kim F. Storm
2008-03-01 10:33 ` Reiner Steib
2008-03-02 2:59 ` Juri Linkov
2008-03-03 13:37 ` Kim F. Storm [this message]
2008-03-03 14:03 ` Stefan Monnier
2008-03-03 23:40 ` Kim F. Storm
2008-03-04 15:49 ` Stefan Monnier
2008-03-04 18:17 ` Kim F. Storm
2008-03-04 19:29 ` Juri Linkov
2008-03-05 0:29 ` Kim F. Storm
2008-03-04 19:40 ` Reiner Steib
2008-03-05 0:30 ` Kim F. Storm
2008-03-04 21:37 ` Chong Yidong
2008-03-04 21:48 ` Nick Roberts
2008-03-06 0:09 ` Kim F. Storm
2008-03-06 15:18 ` Chong Yidong
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=87lk50c4i5.fsf@kfs-lx.rd.rdm \
--to=storm@cua.dk \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.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 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).