all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Štěpán Němec" <stepnem@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 10150@debbugs.gnu.org, emacs-devel <emacs-devel@gnu.org>
Subject: Re: bug#10150: deactive->inactive, inactivate->deactivate spelling fixes
Date: Tue, 29 Nov 2011 12:47:00 +0100	[thread overview]
Message-ID: <878vmzf8wb.fsf@gmail.com> (raw)
In-Reply-To: <4ED49229.2030107@cs.ucla.edu> (Paul Eggert's message of "Tue, 29 Nov 2011 00:04:57 -0800")

On Tue, 29 Nov 2011 09:04:57 +0100
Paul Eggert wrote:

> On 11/28/11 03:17, Štěpán Němec wrote:
>> By renaming functions and variables without any kind of deprecation
>> procedure (cf. `make-obsolete' and friends),
>
> Sure, we can do deprecation.  Is the usual procedure to do this for
> all visible symbols, or only for the symbols that are documented
> in the manual?

You'd have to ask the maintainers for the definitive answer (emacs-devel
added to the Cc: list); I think it's usually closer to the latter.

IMO all commands, hooks and user variables definitely need deprecation,
the rest should at least be mentioned in NEWS.

-- 
Štěpán



  parent reply	other threads:[~2011-11-29 11:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-27 23:38 bug#10150: deactive->inactive, inactivate->deactivate spelling fixes Paul Eggert
2011-11-28 11:17 ` Štěpán Němec
2011-11-29  8:04   ` Paul Eggert
2011-11-29 11:47     ` Štěpán Němec
2011-11-29 11:47     ` Štěpán Němec [this message]
2011-12-31  6:12       ` Paul Eggert
2012-01-03 16:55         ` Štěpán Němec
2012-01-12  8:12           ` Paul Eggert
2012-01-12 16:08             ` Štěpán Němec
2011-11-28 20:46 ` Wolfgang Jenkner
2011-11-29  4:52   ` Chong Yidong
2011-11-29 15:37     ` Drew Adams
2011-11-29  8:33   ` Paul Eggert
2012-07-29  7:19 ` Paul Eggert
2012-08-02  0:51 ` Katsumi Yamaoka
2012-08-02  1:36   ` Paul Eggert

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=878vmzf8wb.fsf@gmail.com \
    --to=stepnem@gmail.com \
    --cc=10150@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --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.
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.