That is part of it. IIRC, the only requirement SVN had was that the file had to have consistent line endings.
How SVN stored diffs and whole files for quick and partial retrieval I do not know. After the svn2git migration some of our files came out one way or the other. I think I even remember one or two causing Visual Studio to complain that the file had mixed line endings. .gitattributes was added to the tree to try and clear all this up. ----- Rom -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Robert Miles Sent: Tuesday, February 26, 2013 8:25 PM To: [email protected] Subject: Re: [boinc_dev] boinc_dev Digest, Vol 105, Issue 51 The line feed issues are likely to depend on what operating system the files were created under. Windows. Linux/UNIX, and MacOS use different ways of marking the ends of lines in text files. > Date: Tue, 26 Feb 2013 10:07:27 -0500 > From: Oliver Bock <[email protected]> > Subject: Re: [boinc_dev] BOINC-v2 Git Repo Updated > > Hi Rom, > > On 2/25/13 18:14 , Rom Walton wrote: > >> It turns out line feed issues from the svn2git migration were my >> biggest nemesis. > What exactly do you mean by "line feed issues"? This might be the > actual root cause of the problem since content is being modified. I > haven't yet checked what the actual differences I found are... > > Any idea where these line feed issues come from? Since you're using > .gitattributes, did you make sure all v2 files fit those rules? > > Cheers, > Oliver > _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
