Re: Results of: [VOTE] New space-before-parens style

Julian Foad <julianfoad@btopenworld.com> writes:
> Now I'm getting scared. We don't have the tools to handle this. Your
> diff is against r18463, and HEAD is r18468, and 17 files have been
> changed in that time.

Oh, you don't think I'd just commit the old patch, do you? I updated
my tree and re-ran the entire process. That's why they call us
"programmers" :-).

> * "svn up" to ignore whitespace. Anyone? Also, how important is
> this? It's pretty much essential unless all developers have clean WCs
> at the time they update to this particular revision. There is a
> particular danger in that there is no automated way to revert an "svn
> update" that suffers conflicts.

Nah, no danger, conflicts save all possible versions of the files, so
the user has everything needed for resolution.

Anyway, too late, r18471. It's not like we didn't know what we were
getting into. Adjusting outstanding patches to meet the new codebase
should be pretty trivial, though.

-Karl

-- 
www.collab.net  <>  CollabNet  |  Distributed Development On Demand
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org