Re: Automatically tidying up code upon checkin

On Thu, 15 Sep 2005 17:31:38 +0200, Ryan Schmidt
<subversion-2005@ryandesign.com> wrote:

>And then Kevin makes additional changes to his code and tries to
>commit that, and it doesn't work because his working copy is out-of-
>date. Then he does an update and gets conflicts because the pretty-
>printed old code is likely not mergeable with his non-pretty-printed
>new code. It's just one problem after another.
>
>Best answer is to Just Say No to automatic repository-side pretty-
>printing. Do it on the client side if you must do it at all.

Surely the same thing is going to happen with two developers working
on the code, if one remembers to pretty-print and one doesn't? Just
because one of the 'developers' is now an automated process doesn't
make it any different, and it doesn't really make it repository-side,
either. It's just another client - the process just happens to be
running on the same hardware as where the repository resides.

Greg
[Playing, to an extent, Devil's advocate. IMHO, I'd create a
pre-commit hook to stop any commits that didn't meet the prettified
format. IIRC, that's what the book recommends, anyway]

-- 
This post represents the views of the author and does
not necessarily accurately represent the views of BT.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org