On Sep 11, 2012, at 09:48, Laurent Alebarde wrote: > Le 11/09/2012 15:49, Stefan Sperling a écrit : >> >> What do you really need this feature for? I'm interested in learning >> more about your actual use case, the actual problem you're trying to >> solve, rather than what git's solution to your problem is. Maybe if >> I knew more about the problem itself I could give you a better answer. >> And maybe we can add some feature to svn to solve your problem, once we >> understand the problem. > Sure, you are right. At present time, my use cases are : > 1) Automatic coding style refactoring so that developpers remain happy with > what they are used to : indentation, naming, layout, etc.
The usual Subversion solution for this is to either a) write a pre-commit hook that verifies that the code conforms to the style guidelines, and rejects the commit if it does not; or b) write a post-commit hook that converts code to the required style and commits this in a second revision > 2) Automatic doxygen comments generation. Here too the usual Subversion solution is to have a post-commit hook generate this and then commit it. Another common answer is that things that can be generated should not be stored in the repository. > 3) Add information in the code in the workspace, from tags included in the > repository I don't understand... could you give an example?
