RE: Strange CVS problem (help!!!)

[Patrik Stridvall]

> "Dimitrie O. Paun"  writes:
> > Not quite. If you run the tool on every commit (which is in
>
> effect what's
> > happening now), you almost guarantee that many people
>
> contributing code
> > will experience conflicts on a *daily* basis. If you run
>
> the tool once
> > once a year, I will experience the conflict only then. And
>
> I will be so
> > much happy.
>
> Well yes, that's what I meant by saying that the tool is "useless". If
> I'm the only one who can use it, and then only once a year, we don't
> really need it.

As I can see it either we enforce no trailing whitespace or we
do not. I can't see any reasonable middle ground.

I'm of course for no trailing whitespace. :-)
However I'm not going to start a new flamewar other it...
> And in fact we should probably remove it so that other
> people are not tempted to use it...

The orginal reason for winapi_cleanup was to convert the \r\n 
that I got while editing in Micrsoft Developer studio
to \n.

But I can modify it the so it only does that.

It should probably remove trailing whitespace at lines
ending in \ though since some compilers choke on that.

Strange CVS problem (help!!!)

[Alexandre Julliard]

Patrik Stridvall  writes:
> The orginal reason for winapi_cleanup was to convert the \r\n 
> that I got while editing in Micrsoft Developer studio
> to \n.
>
> But I can modify it the so it only does that.
>
> It should probably remove trailing whitespace at lines
> ending in \ though since some compilers choke on that.

Sure, the idea of a cleanup tool is a good thing, it just should only
do the cleanups that we all agree on. Myself I'm especially interested
in an automatic cleanup of C++ comments...