mirrors/emacs
1
Fork 0
mirror of git://git.sv.gnu.org/emacs.git synced 2026-01-20 11:33:09 -08:00
Code Issues Projects Releases Wiki Activity

Prefer HTTPS to HTTP for gnu.org

Browse source 
This fixes some URLs I omitted from my previous pass,
notably those in lists.gnu.org.  Although lists.gnu.org
does not yet support TLS 1.1, TLS 1.0 is better than nothing.
* lisp/erc/erc.el (erc-official-location):
* lisp/mail/emacsbug.el (report-emacs-bug):
Use https:, not http:.
This commit is contained in:
Paul Eggert 2017-10-01 19:53:56 -07:00
parent 8cdd8b920a
commit 5172fa02cc
114 changed files with 648 additions and 649 deletions
Download patch file Download diff file Expand all files Collapse all files

2
admin/ChangeLog.1
View file

@ -1547,7 +1547,7 @@
* make-tarball.txt: Suggest 'autoreconf -I m4 --force'
rather than doing rm and autoconf by hand. See
<http://lists.gnu.org/archive/html/emacs-devel/2011-01/msg00673.html>.
<https://lists.gnu.org/archive/html/emacs-devel/2011-01/msg00673.html>.
2011-01-17 Paul Eggert <eggert@cs.ucla.edu>

2
admin/notes/bugtracker
View file

@ -552,7 +552,7 @@ https://savannah.nongnu.org/projects/listhelper
An "X-Debbugs-Envelope-To" header is used to keep track of where the
mail was actually bound for:
http://lists.gnu.org/archive/html/emacs-devel/2009-11/msg01211.html
https://lists.gnu.org/archive/html/emacs-devel/2009-11/msg01211.html
** Mailing list recipient/sender filters.
The following mailman filters are useful to stop messages being

20
admin/notes/copyright
View file

@ -86,7 +86,7 @@ in a README file in each directory with images. (Legal advice says
that we need not add notices to each image file individually, if they
allow for that.). It is recommended to use the word "convert" to
describe the automatic process of changing an image from one format to
another (http://lists.gnu.org/archive/html/emacs-devel/2007-02/msg00618.html).
another (https://lists.gnu.org/archive/html/emacs-devel/2007-02/msg00618.html).
When installing a file with an "unusual" license (after checking first
@ -159,7 +159,7 @@ etc/future-bug
etc/letter.pbm,letter.xpm
- trivial, no notice needed.
<http://lists.gnu.org/archive/html/emacs-devel/2007-02/msg00324.html>
<https://lists.gnu.org/archive/html/emacs-devel/2007-02/msg00324.html>
etc/FTP, ORDERS
- trivial (at time of writing), no license needed
@ -214,7 +214,7 @@ lib-src/etags.c
from a legal point of view.
lisp/cedet/semantic/imenu.el
- See http://lists.gnu.org/archive/html/emacs-devel/2010-03/msg00410.html
- See https://lists.gnu.org/archive/html/emacs-devel/2010-03/msg00410.html
in which Eric Ludlam established that the remaining contributions
from authors other than himself were negligible.
@ -223,7 +223,7 @@ lisp/play/tetris.el
(2007/1) there is no problem with our use of the name "tetris" or
the concept.
rms: "My understanding is that game rules as such are not copyrightable."
<http://lists.gnu.org/archive/html/emacs-devel/2007-01/msg00960.html>
<https://lists.gnu.org/archive/html/emacs-devel/2007-01/msg00960.html>
rms: Legal advice is that we are ok and need not worry about this.
@ -307,8 +307,8 @@ doc/*/*.texi - All manuals should be under GFDL (but see below), and
should include a copy of it, so that they can be distributed
separately. faq.texi has a different license, for some reason no-one
can remember.
http://lists.gnu.org/archive/html/emacs-devel/2007-04/msg00583.html
http://lists.gnu.org/archive/html/emacs-devel/2007-04/msg00618.html
https://lists.gnu.org/archive/html/emacs-devel/2007-04/msg00583.html
https://lists.gnu.org/archive/html/emacs-devel/2007-04/msg00618.html
doc/misc/mh-e.texi is dual-licensed (GPL and GFDL) per agreement with
FSF (reconfirmed by rms Aug 25 2008). Discussion with
@ -397,7 +397,7 @@ lisp/term/README
Accordingly, FSF copyright was added.
src/unexhp9k800.c
http://lists.gnu.org/archive/html/emacs-devel/2007-02/msg00138.html
https://lists.gnu.org/archive/html/emacs-devel/2007-02/msg00138.html
- briefly removed due to legal uncertainly Jan-Mar 2007. The
relevant assignment is under "hp9k800" in copyright.list. File was
written by John V. Morris at HP, and disclaimed by the author and
@ -406,10 +406,10 @@ src/unexhp9k800.c
lisp/progmodes/python.el
Dave Love alerted us to a potential legal problem:
http://lists.gnu.org/archive/html/emacs-pretest-bug/2007-04/msg00459.html
https://lists.gnu.org/archive/html/emacs-pretest-bug/2007-04/msg00459.html
On consultation with a lawyer, we found there was no problem:
http://lists.gnu.org/archive/html/emacs-devel/2007-05/msg00466.html
https://lists.gnu.org/archive/html/emacs-devel/2007-05/msg00466.html
** Issues that are "fixed" for the release of Emacs 22, but we may
@ -527,7 +527,7 @@ None known.
The EMACS_22_BASE branch was changed to GPLv3 (or later) 2007/07/25.
Some notes:
(see http://lists.gnu.org/archive/html/emacs-devel/2007-07/msg01431.html)
(see https://lists.gnu.org/archive/html/emacs-devel/2007-07/msg01431.html)
1. There are some files in the Emacs tree which are not part of Emacs (eg
those included from Gnulib). These are all copyright FSF and (at time

12
admin/notes/documentation
View file

@ -5,7 +5,7 @@ Some documentation tips culled from emacs-devel postings.
** Manual indices
http://lists.gnu.org/archive/html/emacs-devel/2008-10/msg00400.html
https://lists.gnu.org/archive/html/emacs-devel/2008-10/msg00400.html
For example, this text:
@ -51,7 +51,7 @@ combine them into a single entry, e.g.:
** Point is a proper name
http://lists.gnu.org/archive/html/emacs-devel/2008-10/msg00414.html
https://lists.gnu.org/archive/html/emacs-devel/2008-10/msg00414.html
In Emacs tradition, we treat "point" as a proper name when it refers
to the current editing location. It should not have an article.
@ -65,7 +65,7 @@ referring to point, please fix it.
** Don't use passive verbs
http://lists.gnu.org/archive/html/emacs-devel/2008-10/msg00414.html
https://lists.gnu.org/archive/html/emacs-devel/2008-10/msg00414.html
Documentation is clearer if it avoids the passive voice whenever
possible. For example, rather than saying "Point does not move", say
@ -80,7 +80,7 @@ often provides important information which makes the text clearer, too.
*** Why Antinews is useful
http://lists.gnu.org/archive/html/emacs-devel/2008-11/msg00893.html
https://lists.gnu.org/archive/html/emacs-devel/2008-11/msg00893.html
The usefulness of Antinews is to help people who buy the printed
manual and are still using the previous Emacs version. That's why we
@ -91,7 +91,7 @@ Of course, we try to make it amusing as well.
*** Don't mention in Antinews too many features absent in old versions
http://lists.gnu.org/archive/html/emacs-devel/2008-11/msg01054.html
https://lists.gnu.org/archive/html/emacs-devel/2008-11/msg01054.html
Since the purpose of Antinews is to help people use the previous Emacs
version, there is usually no need to mention features that are simply
@ -114,4 +114,4 @@ In those cases, the user might have trouble figuring out how to use
the old version without some sort of help.
** To indicate possession, write Emacs's rather than Emacs'.
http://lists.gnu.org/archive/html/emacs-devel/2012-02/msg00649.html
https://lists.gnu.org/archive/html/emacs-devel/2012-02/msg00649.html

4
admin/notes/repo
View file

@ -11,7 +11,7 @@ install it only on the emacs-24 branch, not on the master as well.
Installing things manually into more than one branch makes merges more
difficult.
http://lists.gnu.org/archive/html/emacs-devel/2010-03/msg01124.html
https://lists.gnu.org/archive/html/emacs-devel/2010-03/msg01124.html
The exception is, if you know that the change will be difficult to
merge to the master (eg because the master code has changed a lot).
@ -40,7 +40,7 @@ so interim merges are unnecessary.
Or use shelves; or rebase; or do something else. See the thread for
yet another fun excursion into the exciting world of version control.
http://lists.gnu.org/archive/html/emacs-devel/2010-04/msg00086.html
https://lists.gnu.org/archive/html/emacs-devel/2010-04/msg00086.html
* Installing changes from gnulib

2
admin/notes/tags
View file

@ -3,7 +3,7 @@ Apparently these date from ye olden days, when tags were common
to several GNU projects. So many of them had no relevance to Emacs,
and hence were removed. See:
http://lists.gnu.org/archive/html/emacs-devel/2012-04/msg00042.html
https://lists.gnu.org/archive/html/emacs-devel/2012-04/msg00042.html
In the unlikely event that you need them, the removed tags were:

3
admin/notes/versioning
View file

@ -1,6 +1,6 @@
GNU EMACS VERSIONING -*- org -*-
Ref: http://lists.gnu.org/archive/html/emacs-devel/2014-09/msg00872.html
Ref: https://lists.gnu.org/archive/html/emacs-devel/2014-09/msg00872.html
Emacs version numbers have the form
@ -27,4 +27,3 @@ unexpected last-minute problem occurs.
The development version for a new major release has "minor" = 0.
The development version for a new minor release has "minor" = that of
the previous release.

2
admin/notes/years
View file

@ -37,4 +37,4 @@ but should keep the full list in a comment in the source.
--RMS, 2005-07-13
[1] Note that this includes 2001 - see
<http://lists.gnu.org/archive/html/emacs-pretest-bug/2006-12/msg00119.html>
<https://lists.gnu.org/archive/html/emacs-pretest-bug/2006-12/msg00119.html>

4
admin/nt/README-ftp-server
View file

@ -233,12 +233,12 @@ See the end of the file for license conditions.
related to the Windows port of Emacs. For information about the
list, see this Web page:
http://lists.gnu.org/mailman/listinfo/help-emacs-windows
https://lists.gnu.org/mailman/listinfo/help-emacs-windows
To ask questions on the mailing list, send email to
help-emacs-windows@gnu.org. (You don't need to subscribe for that.)
To subscribe to the list or unsubscribe from it, fill the form you
find at http://mail.gnu.org/mailman/listinfo/help-emacs-windows as
find at https://mail.gnu.org/mailman/listinfo/help-emacs-windows as
explained there.
Another valuable source of information and help which should not be