On Sat, 18 Jan 2025 at 15:35, sebb <seb...@gmail.com> wrote: > > On Sat, 18 Jan 2025 at 14:31, Gary Gregory <garydgreg...@gmail.com> wrote: > > > > Git has a setting for that called core.autocrlf and it seems we need to > > tell people exactly how to use it and put that in our Readme files and > > source web pages. We should explain how to use it on macOS, Windows, Linux. > > The problem is that people don't always follow the instructions, and > may forget to re-apply them following re-installation.
It looks like commons-build might be a culprit ... > Ideally we need something that is part of the repo checkout. Has anyone experience of using .gitattributes? That looks as though it might be a solution. > > We probably also need to point out using dos2unix on Windows to clean up > > messes. > > The method suggested by Gilles in > https://betterstack.com/community/questions/git-replacing-lf-with-crlf/ > looks better However, I have just tried it, and it does not work for me. > And I think we need to add a check to detect commits that break things. > > > Gary > > > > On Sat, Jan 18, 2025, 08:46 sebb <seb...@gmail.com> wrote: > > > > > Several Git repos have files with CRLF line endings even when checked > > > out on Unix or macOS. > > > > > > This can cause problems when editing, and can cause large commit diff > > > emails which obscure the actual change. > > > > > > I'm thinking it might be useful to add a Checkstyle rule to detect such > > > files. > > > > > > And/or maybe there is a way to ensure text files don't get the wrong EOL? > > > > > > Sebb > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
