+1 to a gradual perltidy 2012/3/8 Fischer, Katrin <katrin.fisc...@bsz-bw.de>
> ** > > I agree with Chris C. and Chris N. - I think what we would win does not > outweigh the loss of history. > > Katrin > > -----Ursprüngliche Nachricht----- > Von: koha-devel-boun...@lists.koha-community.org im Auftrag von Chris > Nighswonger > Gesendet: Do 08.03.2012 19:26 > An: Chris Cormack > Cc: koha-devel@lists.koha-community.org > Betreff: Re: [Koha-devel] Koha 3.8 release schedule & perltidy process > > > 2012/3/8 Chris Cormack <ch...@bigballofwax.co.nz> > > > My counter proposal is tidy as you go. Fix code as you touch it. > > > > With vim (and other editors) you can easily tidy a block, doing that as > > code is changed would be my preference. > > > > I'd prefer a "pay-as-you-go" approach as well. We could simply require all > work to be tidied before submitting. > > Slow? Yes, but not nearly as messy and preserves the history. > > Kind Regards, > Chris > > > _______________________________________________ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -- Jared Camins-Esakov Bibliographer, C & P Bibliography Services, LLC (phone) +1 (917) 727-3445 (e-mail) jcam...@cpbibliography.com (web) http://www.cpbibliography.com/
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
