xt
month or
two, I thought this would be a great opportunity for us to have
a code
clean
up drive. Looking through the code base it is apparent that we
have
some
code atrophy. As we have re-organized, rewritten, or replaced
functionality, in many cases the former code has been left in
t
breaks, it is difficult to see what caused the problem.
>>>>
>>>> I am all in for a code cleanup. I am just not sure that doing it
>> together
>>>> with the source code move is the best timing.
>>>>
>>>> Greetings
>>
see what caused the problem.
> >>
> >> I am all in for a code cleanup. I am just not sure that doing it
> together
> >> with the source code move is the best timing.
> >>
> >> Greetings
> >> Torben
> >>
> >> 2010/12/10 Mich
gt;>> Greetings
>>> Torben
>>>
>>> 2010/12/10 Michael MacFadden
>>>
>>>> All,
>>>>
>>>> As we ponder moving our source code over to Apache in the next month or
>>>> two, I thought this would be a great opp
e that doing it together
>> with the source code move is the best timing.
>>
>> Greetings
>> Torben
>>
>> 2010/12/10 Michael MacFadden
>>
>>> All,
>>>
>>> As we ponder moving our source code over to Apache in the next month or
>>
er
> with the source code move is the best timing.
>
> Greetings
> Torben
>
> 2010/12/10 Michael MacFadden
>
>> All,
>>
>> As we ponder moving our source code over to Apache in the next month or
>> two, I thought this would be a great opportunity for us t
s would be a great opportunity for us to have a code clean
> up drive. Looking through the code base it is apparent that we have some
> code atrophy. As we have re-organized, rewritten, or replaced
> functionality, in many cases the former code has been left in the code base.
>
> D
All,
As we ponder moving our source code over to Apache in the next month or two, I
thought this would be a great opportunity for us to have a code clean up drive.
Looking through the code base it is apparent that we have some code atrophy.
As we have re-organized, rewritten, or replaced
