archives/freedoom
2
0
Fork 0
mirror of https://github.com/freedoom/freedoom.git synced 2025-09-01 13:25:46 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

README: remove last two paragraphs

Browse source 
These are complicated and nobody follows them.
This commit is contained in:
Mike Swanson 2019-09-06 11:47:53 -07:00
parent e13db68259
commit 827153a16f
1 changed files with 0 additions and 14 deletions
Download patch file Download diff file Expand all files Collapse all files

14
README.adoc
View file

@ -254,17 +254,3 @@ version control systems, adopted by projects such as Linux and Git.
For an explanation of this style, see For an explanation of this style, see
https://chris.beams.io/posts/git-commit/[How to Write a Git Commit https://chris.beams.io/posts/git-commit/[How to Write a Git Commit
Message]. Message].
The commit `2017-02-20T01:52:35Z!mikeonthecomputer@gmail.com` is a
good example of a properly-written commit.
Do not use commit hashes to refer to other commits. Use other kinds
of pointers, simple ones like “my previous commit” might suffice, or
use http://esr.ibiblio.org/?p=3872[action stamps], which can improve
the meaningfulness of commit identifiers if the repository history is
rewritten (this has happened at least twice!), or if the repository is
converted to another VCS (this happened once before). At the time of
writing (February 2017), core Git does not yet have a mechanism to
output this format, but you may use a
https://gist.github.com/chungy/195f53bfb9253584e596[shell script] and
place it in your `$PATH` to achieve some ease in generating them.