[at-spi] Do not use ChangeLog file any more
- From: Li Yuan <liyuan src gnome org>
- To: svn-commits-list gnome org
- Subject: [at-spi] Do not use ChangeLog file any more
- Date: Thu, 21 May 2009 05:36:30 -0400 (EDT)
commit 43108619c295685d81b7f50b5874943441e7b141
Author: Li Yuan <li yuan sun com>
Date: Thu May 21 17:42:59 2009 +0800
Do not use ChangeLog file any more
Bug #583422. With move to git, do not use ChangeLog anymore.
---
ChangeLog | 6 ++++++
README.commits | 29 +++++++++++++++++++++++++++++
2 files changed, 35 insertions(+), 0 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index 781d5b7..dd52628 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+=== ChangeLog discontinued ===
+
+ With the move to git, at-spi is switching from a ChangeLog file
+ to relying on commit messages to provide change history. Please
+ see README.commits for guidance on the expected message format.
+
2009-03-16 Li Yuan <li yuan sun com>
* NEWS:
diff --git a/README.commits b/README.commits
new file mode 100644
index 0000000..f11e361
--- /dev/null
+++ b/README.commits
@@ -0,0 +1,29 @@
+At-spi is part of the GNOME git repository. With git, we no longer
+maintain a ChangeLog file, but you are expected to produce a meaningful
+commit message. Changes without a sufficient commit message will be
+reverted. The expected format for git commit messages is as follows:
+
+=== 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 (it will work without the
+ second newline, but that is not nice for the interfaces).
+
+ - 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 period either. Don't exceed
+ 72 characters.
+
+ - The main description (the body) is normal prose and should use normal
+ punctuation and capital letters where appropriate. Normally, for patches
+ sent to a mailing list it's copied from there.
+
+ - When committing code on behalf of others use the --author option, e.g.
+ git commit -a --author "Joe Coder <joe coder org>" and --signoff.
+
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]