From: Stefan Kangas <stefan@marxist.se>
To: Roland Winkler <winkler@gnu.org>
Cc: Glenn Morris <rgm@gnu.org>, 21563@debbugs.gnu.org
Subject: bug#21563: 24.5; discourage load-hook variables
Date: Tue, 20 Oct 2020 17:16:50 +0000 [thread overview]
Message-ID: <CADwFkmn0PY-0h+9eH4VW1vfBHyWN38GRahO9Lz_CtM3Wds4tEQ@mail.gmail.com> (raw)
In-Reply-To: <87tv169v0z.fsf@stefankangas.se> (Stefan Kangas's message of "Sun, 26 Apr 2020 16:33:16 +0200")
Stefan Kangas <stefan@marxist.se> writes:
>>> > I did this years ago for a few modes; eg dd210a6, 041e909, but never got
>>> > round to doing the rest. As I said in https://debbugs.gnu.org/24491#8, I
>>> > see no need to keep any *-load-hooks.
>>>
>>> I see you have now done the rest on master. Does that mean that this
>>> bug can also be closed? Thanks.
>>
>> Thanks for taking care of this. I am glad the load hooks are gone.
>>>>From my perspective the bug can be closed.
>
> No further comments within a week, so I'm closing the bug now.
Some load-hooks were never obsoleted here. I've now marked them
obsolete on the master branch in commit 6c58d90042.
next prev parent reply other threads:[~2020-10-20 17:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 18:57 bug#21563: 24.5; discourage load-hook variables Roland Winkler
2020-01-15 19:32 ` Stefan Kangas
2020-01-15 20:21 ` Drew Adams
2020-01-15 20:42 ` Stefan Kangas
2020-01-16 0:27 ` Roland Winkler
2020-01-15 22:06 ` Glenn Morris
2020-01-16 0:03 ` Stefan Kangas
2020-01-16 0:24 ` Drew Adams
2020-01-16 0:54 ` Stefan Kangas
2020-01-16 3:56 ` Drew Adams
2020-01-16 13:33 ` Stefan Kangas
2020-01-16 16:15 ` Drew Adams
2020-01-16 20:30 ` Stefan Kangas
2020-01-16 21:08 ` Drew Adams
2020-01-16 0:31 ` Stefan Kangas
2020-04-16 4:14 ` Stefan Kangas
2020-04-16 9:07 ` Roland Winkler
2020-04-26 14:33 ` Stefan Kangas
2020-10-20 17:16 ` Stefan Kangas [this message]
2020-01-16 11:49 ` Mauro Aranda
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=CADwFkmn0PY-0h+9eH4VW1vfBHyWN38GRahO9Lz_CtM3Wds4tEQ@mail.gmail.com \
--to=stefan@marxist.se \
--cc=21563@debbugs.gnu.org \
--cc=rgm@gnu.org \
--cc=winkler@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 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).