|
From: Luigi B. <bal...@ma...> - 2002-04-29 20:07:08
|
At 6:58 PM +0200 4/29/02, Andre Louw wrote: >I need some help. We all have our specific idiosyncrasies, one of mine is >that I'm hooked on my indentation and general appearance of my source files. It seems to be a widespread disease here :) >Unfortunately I'm running into trouble when checking in or out from >QuantLib's CVS. >Any file that I worked on that somebody else worked on as well I get >conflicts, 99% of the time because of >indentation. Unfortunately this works vice-versa as well. >I haven't really checked but I'm pretty sure there must be some automated >way of getting this to work. >IOW get a common .indent.pro on the CVS server, which all files are >converted to when checked in, >and a personal .indent.pro which is used when checking out. Andre, I just checked a fe CVS resources on line. It is possible to run a program upon commit and/or update: however, the programs are run only after the cvs operation succesfully terminates---one can't pipe the cvs incoming/outgoing data through them :( >Luigi, > >I used the indent.pro file you sent me a while ago but I've noticed the >indent >option --braces-on-struct-decl-line tends to break c++ files!!!! Ouch. This is a strange one: shuffling around whitespace shouldn't break C++ code... What exactly happens to the source? Luigi -- |