On 10 Dec 2003, David Crossley wrote: > Stephan Michels wrote: > > > > after I made some positive experiences with jalopy, an open source > > code formatter, I want to offer install jalopy with a proposal > > for the our code convention. > > What do you mean by "install"? In our CVS? Or does each committer > who wants to help, need to have it installed locally?
I mean to commit. I have now committed jalopy to the cocoon-2.1 repository. > > This should be a welcome alternative to the various 'organize imports' > > and 'dos2unix' etc. > > > > What do'ya think? > > As we discussed in the other "Whitepace" thread [1] there are > many issues with this, so we need to tread carefully. Imagine > that someone was doing major work on a certain component. When > they do a 'cvs update' then they would get massive cvs conflicts. If the source code in the CVS is well formated, this 'worst case' couldn't happen. > Perhaps we should practise with the cocoon-2.2 repository. > > I am not sure what POLL means, but yes i am interested. > Thanks for exploring this. I only want to hear your opinions. > [1] http://marc.theaimsgroup.com/?t=106843997700002 I missed that. Stephan.
