Changes

Jump to: navigation, search

Committing policies

265 bytes added, 13:04, 30 July 2014
m
Check
* It is not necessary to describe minute details about the change nor the files that are affected because that information is already stored by Git and can be viewed with "git diff".
* When committing contributed code, the author should be credited using the --author option.
* If you want to refer to another commit, use the commit short hash (6 hexa digits) in square brackets. It will automatically be expanded to a hyperlink by the SourceForge web interface to the repository, e.g.: [http://sourceforge.net/p/gramps/source/ci/d8acf8e875a06cf89b2cc4d59ed63730539244af/ [d8acf8]].Note: the default short hash in git is 7 hexa digits (as produced by `git log --oneline' command), and that WILL NOT WORK with auto-hyperlinking of sourceforge :-(
You can see the last changes with the git log command, an example usage of this command:
git log --oneline
You can also limit the number of entries shown by passing in the '''-n''' flag to svngit. Add '''--stat''' to see the files affected by the commit:
git log -5
 
To credit the contributor of a patch, use:
 
git commit -m 'Commit message' --author='A U Thor <[email protected]>'
==Adding new files==
You can make a test on a local copy:
./autogen.sh PYTHONPATH=../../trunk/src gramps python po/test/po_test.py
where ../.. is the path to your local copy

Navigation menu