This might be a goo dtime to lose history and clean things up.
  When I was in charge of Mono's Winforms we had this problem *bad*. The way I 
dealt with it was to have a check in with nothing but line changes, so if 
someone had old code that needed comparing, they could compare aginst the old 
checkin.
   
  I would suggest doing one checkin that only did reformating, and then doing 
one that only changes line endings.
   
  Does our version control have an option to convet line endings at checkin?
   
  Thanks,
  Dennis
   
   
  > And yes, we can reformat pre-existing code, but you have to be careful not 
to lose history when you do it. Especially when dealing with inconsistent 
line-endings...


       
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile.  Try it now.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
SharpOS-Developers mailing list
SharpOS-Developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sharpos-developers

Reply via email to