On Tue, Jul 20, 2010 at 10:16 AM, Les Mikesell <lesmikesell_at_gmail.com> wrote:
> On 7/20/2010 12:49 AM, Nico Kadel-Garcia wrote:
>> 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.
The EOL problem makes this a seriously broken problem. The wreckage of
the old code is in a clean location, where the changes can be tracked
too, but there is *NO WAY* to "easily see what changed" between files
with unpredictably changing EOL's. With a clean demarcation, you have
a well denoted break point to mark where you'll have to change
procedures to get your diffs.
Received on 2010-07-21 14:12:38 CEST