IntenseFinance/gnucash
3
0
Fork 0
mirror of https://github.com/Gnucash/gnucash.git synced 2025-02-25 18:55:30 -06:00
Code Issues Packages Projects Releases Wiki Activity

Minor updates to README.svn; remove README.patches from gnucash.spec.in.

Browse Source 
Do not demand ChangeLog entries as they are created automagically.


git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@17016 57a11ea4-9604-0410-9ed3-97b8803252fd
This commit is contained in:
Andreas Köhler
2008-03-08 20:04:46 +00:00
parent 5834cb4179
commit 78cb99bf3d
2 changed files with 3 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
README.svn
View File

@@ -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 They have been adapted from the guidelines for gnome-libs by
Miguel de Icaza who adapted them from guidelines written by Miguel de Icaza who adapted them from guidelines written by
Owen Taylor. Owen Taylor.
@@ -47,7 +47,7 @@ When making changes to GnuCash and trying to commit to the repository:
Since you want other people to review your code before it goes in, Since you want other people to review your code before it goes in,
you can submit your changes as a patch to gnucash-devel@gnucash.org. you can submit your changes as a patch to gnucash-devel@gnucash.org.
See README.patches for details. See README for details.
If you are making changes to gnucash SVN, you should be subscribed If you are making changes to gnucash SVN, you should be subscribed
to gnucash-devel@gnucash.org and to gnucash-changes@gnucash.org. to gnucash-devel@gnucash.org and to gnucash-changes@gnucash.org.
@@ -55,14 +55,6 @@ When making changes to GnuCash and trying to commit to the repository:
gnucash-devel@gnucash.org is a good place to ask about intended gnucash-devel@gnucash.org is a good place to ask about intended
changes. 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 + You must not break the build! Never check in changes that do not
compile, install or run. Just because your local tree compiles compile, install or run. Just because your local tree compiles
doesn't mean you are done. The most common way to break the build doesn't mean you are done. The most common way to break the build
@@ -85,12 +77,6 @@ When making changes to GnuCash and trying to commit to the repository:
a branch. Also, please inform the gnucash-devel-list about what you a branch. Also, please inform the gnucash-devel-list about what you
are going to do. 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 + When code is added from new developers, add them to AUTHORS and
to doc/sgml/C/xacc-about.sgml. to doc/sgml/C/xacc-about.sgml.

2
packaging/gnucash.spec.in
View File

@@ -202,7 +202,7 @@ fi
%exclude %{_libdir}/libgnc-backend-postgres* %exclude %{_libdir}/libgnc-backend-postgres*
%endif %endif
%config %{_sysconfdir}/gnucash %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 %doc doc/README.german doc/README.francais doc/guile-hackers.txt
%files devel %files devel