On Tue, Jul 21, 2009 at 3:56 PM, Jeremy Orlow <jor...@google.com> wrote:
> I was suggesting that any scripts that depend on the eol style could set
> the flag on any files it's touching. For example, svn-create-patch could
> set it on all the files that have been modified. This could even be done
> only when running on Windows not under cygwin to
> minimize compatibility issues. But, given that so many of the files already
> have the flag set, it's probably OK to do, right?
>
This isn't really a feasible solution. Among other things, the rules for
what eol-style goes on what file can be complex, it may not be possible to
set this property without first modifying the file's line endings, this
would add runtime penalties and code complexity to a number of scripts, and
users would be surprised to have some of these scripts causing further
modifications to their checkout.
I have sent a message to webkit-dev regarding eol-style, mentioning how we
handle it for Chromium, which is pretty much the way things would have to
work if we wanted to address this issue.
PK
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
