From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 7777@debbugs.gnu.org
Subject: bug#7777: 24.0.50; incompatible change for `directory-abbrev-alist' not in NEWS
Date: Tue, 04 Jan 2011 06:01:58 +0200 [thread overview]
Message-ID: <837helnwp5.fsf@gnu.org> (raw)
In-Reply-To: <2AFD6A500A684D38948C9F1EFE6CF6B3@us.oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <7777@debbugs.gnu.org>
> Date: Mon, 3 Jan 2011 13:44:50 -0800
>
> 1. We're telling users that _every_ value should be different from what _every_
> value was supposed to be before. That's a change for users that they should be
> made aware of, even if such a "should" is in fact vacuous wrt the difference.
It's not a change, it's a doc fix. The doc string is now more
helpful.
> 2. We should tell users, in NEWS, that they do _not_ in fact need to change
> existing values that respected the old rule - in spite of the changed rule.
> They do _not_ need to swap \\` for ^. That is not necessarily obvious to users.
We don't put in NEWS changes that affect only doc strings.
How about if we change the doc string to not sound like a stringent
requirement, but rather as a "note"?
next prev parent reply other threads:[~2011-01-04 4:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 19:49 bug#7777: 24.0.50; incompatible change for `directory-abbrev-alist' not in NEWS Drew Adams
2011-01-03 20:04 ` Andreas Schwab
2011-01-03 21:44 ` Drew Adams
2011-01-03 20:24 ` Eli Zaretskii
2011-01-03 21:44 ` Drew Adams
2011-01-04 4:01 ` Eli Zaretskii [this message]
2011-01-04 4:12 ` Drew Adams
2011-01-07 16:01 ` Eli Zaretskii
2011-01-08 22:01 ` Chong Yidong
2011-01-08 22:35 ` Drew Adams
2011-01-09 4:02 ` Eli Zaretskii
2011-01-13 5:21 ` Chong Yidong
2011-01-28 17:31 ` Chong Yidong
2011-01-03 21:46 ` Sean Sieger
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=837helnwp5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=7777@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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.