#994: Fix SVN properties for git-svn users
--------------------+-------------------------------------------------------
Reporter: Util | Owner: Util
Type: todo | Status: assigned
Priority: normal | Milestone:
Component: none | Version: 1.5.0
Severity: medium | Keywords: git svn git-svn property properties
auto-prop
Lang: | Patch:
Platform: all |
--------------------+-------------------------------------------------------
Comment(by Util):
Everyone in #parrotsketch was keen on solving this with server-side hooks;
The SVN documentation speaks to this: [[BR]] [http://svnbook.red-
bean.com/nightly/en/svn.reposadmin.create.html#svn.reposadmin.create.hooks]
'''Warning'''
While hook scripts can do almost anything, there is one dimension in which
hook script authors should show restraint: do not modify a commit
transaction
using hook scripts. While it might be tempting to use hook scripts to
automatically correct errors, shortcomings, or policy violations present
in the files being committed, doing so can cause problems. Subversion
keeps
client-side caches of certain bits of repository data, and if you change a
commit transaction in this way, those caches become indetectably stale.
This inconsistency can lead to surprising and unexpected behavior.
Instead of modifying the transaction, you should simply validate the
transaction
in the pre-commit hook and reject the commit if it does not meet the
desired
requirements. As a bonus, your users will learn the value of careful,
compliance-minded work habits.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/994#comment:2>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
