Maybe it will be easier for you to treat the Microsoft generated files as binary blobs... these should remain as-is in all platforms, just like any other binary blob. The gitattributes patch I submitted does exactly that, without interfering with the global setting if it you find this configuration helpful.
On Thu, Mar 29, 2012 at 7:37 PM, Alon Bar-Lev <alon.bar...@gmail.com> wrote: > On Thu, Mar 29, 2012 at 7:26 PM, michael-dev <michael-...@fami-braun.de> > wrote: >> Hi, >> >> On Thu, 29 Mar 2012 18:10:24 +0200, Alon Bar-Lev wrote: >>> For example... >>> >>> at your end: >>> --- >>> ./configure >>> make >>> make dist >>> --- >>> >>> at other people end: >>> --- >>> tar -xf <tarball> >>> cp -a openvpn* openvpn*.org >>> cd openvpn* >>> msvc-dev >>> <add a file to project> >>> <save all> >>> <quit> >>> cd .. >>> diff -urNp openvp* openvpn*.org >>> --- >>> >>> will result in a complete change of all microsoft specific files >>> because of the new line issue. >>> is this enough problem? >> >> so why don't use --strip-trailing-cr (diffutils) or something similar >> to avoid this? >> >> So as long as msvc-dev does accept eol=lf input files, storing them as >> eol=lf files is without issue? > > Hi, > > Because I believe that file format should be as-is and these diff/git > magic should be done only when forced, when invalid action was taken. > > Of course all had been better if Microsoft supported keeping the line > format, but this is not the case. > > I want to see a "make dist" containing file format as it should be, > and Microsoft solution and project files should be CRLFed. > > I truly don't understand... there is a simple solution of git to > explicit set eol style on specific files, why not use it? > > And... also avoid using global setting of git, which is invalid anyway > as we maintain several projects which should be independent. > > Alon.
