[anjuta] Update HACKING file to reflect describe the new commit subject line format.
- From: James Liggett <jrliggett src gnome org>
- To: svn-commits-list gnome org
- Subject: [anjuta] Update HACKING file to reflect describe the new commit subject line format.
- Date: Sat, 16 May 2009 04:41:21 -0400 (EDT)
commit 3499eea5cba4929714a29d2a8189f4e3c796da05
Author: James Liggett <jrliggett cox net>
Date: Sat May 16 01:38:28 2009 -0700
Update HACKING file to reflect describe the new commit subject line format.
Reflect recently agreed-upon protocol that suggests that commit subject lines should be preceded by
the name of the plugin or source module that the commit modifies, as is commonly done with many
projects that use git.
---
HACKING | 8 +++++++-
1 files changed, 7 insertions(+), 1 deletions(-)
diff --git a/HACKING b/HACKING
index 2c76bff..ca49c26 100644
--- a/HACKING
+++ b/HACKING
@@ -53,11 +53,17 @@ Log messages:
-------------
Log messages for git should have the following format:
-"A short summary of the changes (should contain bug number)
+"[Plugin/module name]: A short summary of the changes (should contain bug number)
(empty line)
[optional] A more detailed description of the changes made. Can have multiple
lines and should contain patch contributer, etc."
+As an example, a typical commit against the Subversion plugin looks like this:
+
+ Subversion: Don't show a commit number in the info pane if no files are given
+
+ When no files are selected, the commit isn't done and the commit number is just uninitialized junk.
+
Tools:
-----
Anjuta is written using a mixture of C and C++. You will require
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]