summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNiels De Graef <nielsdegraef@gmail.com>2021-01-17 00:05:26 +0000
committerNiels De Graef <nielsdegraef@gmail.com>2021-01-17 00:05:26 +0000
commita40fa1966253dee7e6d30e24372dbea7369f2a04 (patch)
tree075740697a9b75635cb9d5a2e60ef2d61859528e
parent08368207031ab345a0cc949da34b6474e667a94e (diff)
downloadlibsecret-a40fa1966253dee7e6d30e24372dbea7369f2a04.tar.gz
Delete ChangeLog
It’s been discontinued for almost a decade, so time to clean up.
-rw-r--r--ChangeLog32
1 files changed, 0 insertions, 32 deletions
diff --git a/ChangeLog b/ChangeLog
deleted file mode 100644
index 9cdd7c0..0000000
--- a/ChangeLog
+++ /dev/null
@@ -1,32 +0,0 @@
-=== ChangeLog discontinued ===
-
- libsecret relies on commit messages to provide change history. Please
- write commit messages in the following format:
-
-=== begin example commit ===
-
- Short explanation of the commit
-
- Longer explanation explaining exactly what's changed, whether any
- external or private interfaces changed, what bugs were fixed (with bug
- tracker reference if applicable) and so forth. Be concise but not too
- brief.
-
-=== end example commit ===
-
- - Always add a brief description of the commit to the _first_ line of
- the commit and terminate by two newlines. This may be the title of
- a fixed bug, copied from Bugzilla.
-
- - First line (the brief description) must only be one sentence and
- should start with a capital letter unless it starts with a
- lowercase symbol or identifier. Don't use a trailing full stop,
- and don't exceed 72 characters.
-
- - The main description (the body) is normal prose and should use
- normal punctuation and capital letters where appropriate.
-
- - When committing code on behalf of others use the --author option,
- e.g. git commit -a --author "Joe Coder <joe@coder.org>" and
- --signoff.
-