Replace deprecated http://news.php.net URLs with https://news-web.php.net
across archive pages, release notes, and mailing lists documentation.
This addresses the domain migration and enforces HTTPS security for
news server access.
- Removes comments of old pages that will never come online again
- Removes http://gcov.php.net as this website was shut down
- Adds https://windows.php.net
Closes GH-517.
This patch adds some missing newlines, trims some multiple redundant
final newlines into a single one, and trims few redundant leading
newlines.
According to POSIX, a line is a sequence of zero or more non-'<newline>'
characters plus a terminating '<newline>' character. [1] Files should
normally have at least one final newline character.
C89 [2] and later standards [3] mention a final newline:
"A source file that is not empty shall end in a new-line character,
which shall not be immediately preceded by a backslash character."
Although it is not mandatory for all files to have a final newline
fixed, a more consistent and homogeneous approach brings less of commit
differences issues and a better development experience in certain text
editors and IDEs.
[1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206
[2] https://port70.net/~nsz/c/c89/c89-draft.html#2.1.1.2
[3] https://port70.net/~nsz/c/c99/n1256.html#5.1.1.2
As much as I would love to have a working lxr and just point it to aharvey@'s site, I have just commented out them for now, marking them with the ever grep'able XXX label
welcome! A couple of important notes:
- I've largely dropped references to Subversion altogether, even knowing that
php-doc hasn't migrated yet. We may need to put a few more "Git/SVN account"
references in there if php-doc isn't going to be migrated in the near future.
- I've removed the quick start hints from git-php.php after an account request
has been sent in. The documentation there was pretty skimpy anyway and
probably wouldn't have been enough to get a developer going, plus it's harder
to distill the Git workflow into three or four snappy commands and I'm not
really convinced that a form confirmation page is the right place to have
learning materials, since it's a one-time page for most users. Instead I've
replaced them with links to the relevant Wiki pages, which seem more likely
to be the right place for new developers to learn.
News post to come, but I wanted to separate this out for easier review.
