r17016 - gnucash/trunk - Minor updates to README.svn; remove README.patches from gnucash.spec.in.

Andreas Köhler andi5 at cvs.gnucash.org
Sat Mar 8 15:04:47 EST 2008


Author: andi5
Date: 2008-03-08 15:04:46 -0500 (Sat, 08 Mar 2008)
New Revision: 17016
Trac: http://svn.gnucash.org/trac/changeset/17016

Modified:
   gnucash/trunk/README.svn
   gnucash/trunk/packaging/gnucash.spec.in
Log:
Minor updates to README.svn; remove README.patches from gnucash.spec.in.

Do not demand ChangeLog entries as they are created automagically.


Modified: gnucash/trunk/README.svn
===================================================================
--- gnucash/trunk/README.svn	2008-03-08 19:45:28 UTC (rev 17015)
+++ gnucash/trunk/README.svn	2008-03-08 20:04:46 UTC (rev 17016)
@@ -1,4 +1,4 @@
-This file contains guidelines for using Gnucash from Subversion.
+This file contains guidelines for using GnuCash from Subversion.
 They have been adapted from the guidelines for gnome-libs by
 Miguel de Icaza who adapted them from guidelines written by
 Owen Taylor.
@@ -47,7 +47,7 @@
 
    Since you want other people to review your code before it goes in,
    you can submit your changes as a patch to gnucash-devel at gnucash.org.
-   See README.patches for details.
+   See README for details.
 
    If you are making changes to gnucash SVN, you should be subscribed
    to gnucash-devel at gnucash.org and to gnucash-changes at gnucash.org.
@@ -55,14 +55,6 @@
    gnucash-devel at gnucash.org is a good place to ask about intended
    changes.
 
- + There must be a ChangeLog entry for every commit. If you discover that
-   you only committed half the files you meant to and need to fix that
-   up you do not need a new ChangeLog entry.  But in general, ChangeLog
-   entries are mandatory. Changes with out ChangeLog entries will be
-   reverted.
-
- + When you commit, use your ChangeLog entry as the log message.
-
  + You must not break the build! Never check in changes that do not
    compile, install or run. Just because your local tree compiles
    doesn't mean you are done. The most common way to break the build
@@ -85,12 +77,6 @@
    a branch. Also, please inform the gnucash-devel-list about what you
    are going to do.
 
- + The ChangeLog entries should preferably match in date format with
-   the existing entries. You can set how emacs does this by using
-   customize mode:
-
-   - M-x customize
-
  + When code is added from new developers, add them to AUTHORS and
    to doc/sgml/C/xacc-about.sgml.
 

Modified: gnucash/trunk/packaging/gnucash.spec.in
===================================================================
--- gnucash/trunk/packaging/gnucash.spec.in	2008-03-08 19:45:28 UTC (rev 17015)
+++ gnucash/trunk/packaging/gnucash.spec.in	2008-03-08 20:04:46 UTC (rev 17016)
@@ -202,7 +202,7 @@
 %exclude %{_libdir}/libgnc-backend-postgres*
 %endif
 %config %{_sysconfdir}/gnucash
-%doc AUTHORS COPYING ChangeLog* DOCUMENTERS HACKING LICENSE NEWS README README.patches
+%doc AUTHORS COPYING ChangeLog* DOCUMENTERS HACKING LICENSE NEWS README
 %doc doc/README.german doc/README.francais doc/guile-hackers.txt
 
 %files devel



More information about the gnucash-changes mailing list