]> git.evergreen-ils.org Git - Evergreen.git/commit
FEATURE: Renew with Specific Due Date option for Items Out interface. DEV NOTES...
authorphasefx <phasefx@dcc99617-32d9-48b4-a31d-7c20da2025e4>
Mon, 2 Nov 2009 03:07:37 +0000 (03:07 +0000)
committerphasefx <phasefx@dcc99617-32d9-48b4-a31d-7c20da2025e4>
Mon, 2 Nov 2009 03:07:37 +0000 (03:07 +0000)
commit95c32e215d883b38613a02964c4dda2101d607bc
tree014820beaad92d978474506c84ec5d80d433e1c4
parent1d3e042ab53f2c9305099611078f8154f4d620d0
FEATURE: Renew with Specific Due Date option for Items Out interface.  DEV NOTES: Some refactoring.  Would this style of commit message be useful for change logs?  Some keywords like FEATURE or BUGFIX for stuff meant to be more widely read?  Or alternately, we could use development branches for intermediate work/commits, and reserve trunk and the release branches for changelog worthy commits?  I personally don't mind reviewing 'typo' and 'oops' changesets that fly by.  :)

git-svn-id: svn://svn.open-ils.org/ILS/trunk@14716 dcc99617-32d9-48b4-a31d-7c20da2025e4
Open-ILS/web/opac/locale/en-US/lang.dtd
Open-ILS/xul/staff_client/server/locale/en-US/patron.properties
Open-ILS/xul/staff_client/server/patron/items.js
Open-ILS/xul/staff_client/server/patron/items_overlay.xul