Article explaining why .gitattributes is important for configuring a consistent end of file ending in a git repository used by multiple team members on different OSes.
ASP.NET? The microsoft technology? That runs mostly on IIS? Yeah, that’s not a good example.
This approach is particularly absurd once you take into account the fact that Git supports line ending normalization, and it supports configuring which newline is used when checking out source code not only in a per-repository basis but also on a per-user and even per-local repository basis.
I find it absurd to make a plaidoyer to all git users to add another file to their repo to placate those unable, unwilling, or ignorant to adhere the standard.
ASP.NET? The microsoft technology? That runs mostly on IIS?
No, by ASP.NET I was referring to ASP.NET Core, whose latest LTS version was released along .NET 8.
I find it absurd to make a plaidoyer to all git users to add another file to their repo to placate those unable, unwilling, or ignorant to adhere the standard.
You only speak for yourself, and your comment clearly showed you were ignorant of some basic usecases that are behind the feature you were criticizing.
ASP.NET? The microsoft technology? That runs mostly on IIS? Yeah, that’s not a good example.
I find it absurd to make a plaidoyer to all git users to add another file to their repo to placate those unable, unwilling, or ignorant to adhere the standard.
No, by ASP.NET I was referring to ASP.NET Core, whose latest LTS version was released along .NET 8.
You only speak for yourself, and your comment clearly showed you were ignorant of some basic usecases that are behind the feature you were criticizing.