On 7/20/2010 12:49 AM, Nico Kadel-Garcia wrote:
> On Tue, Jul 20, 2010 at 12:26 AM, Les Mikesell<lesmikesell_at_gmail.com> wrote:
>> On 7/19/2010 10:10 PM, Kitching, Simon wrote:
>>>
>>> Ah well, as it appears that nobody here knows the answer I'll just have
>>> to do it the ugly way: try to get the svn repo administrator to install
>>> some hooks to prevent this occurring in future, and then install cygwin
>>> on somebody's windows PC to script the adding of eol-style=native to
>>> relevant existing files.
>>
>> Maybe you could write your script to check for the need for the change to
>> run on linux but instead of setting the property there, output a batch file
>> of the commands to be executed, transfer the file to windows box (perhaps by
>> committing, and checking back out there with the correct eol's), and then
>> run the commands from the windows side.
>
> Look, *BREAK* the history. History is overvalued: Make a clean tag
> with your final pre-switchover release, with a note explaining what
> happened, and make an entirely new repository or branch with entirely
> imported code. It will be much cleaner to track and follow what
> happened without trying to back-revise history of mixed EOL
> configurations.
I have to disagree very much with this. The ability to easily see what
changed between any two points is most of the value of using version
control systems. Sometimes you won't know why the old way was better
until long after you've forgotten the details of the changes - or the
person who made them may no longer be around.
--
Les Mikesell
lesmikesell_at_gmail.com
Received on 2010-07-20 16:18:43 CEST