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
The $Id$ keywords were used in Subversion where they can be substituted
with filename, last revision number change, last changed date, and last
user who changed it.
In Git this functionality is different and can be done with Git attribute
ident. These need to be defined manually for each file in the
.gitattributes file and are afterwards replaced with 40-character
hexadecimal blob object name which is based only on the particular file
contents.
This patch simplifies handling of $Id$ keywords by removing them since
they are not used anymore.
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.
- Add "I know which licenses PHP projects use, and will develop my code using
them" checkbox to the cvs-request form
# Patch by Judy Taylor <@uk.ibm.com> and Zoe
