Create gitattributes file specifying proper line endings

[tobiasdiez]

If you checkout sage on Windows, the line endings are wrong (depending on the core.autocrlf setting).

This PR adds a .gitattributes file which specifies the correct line ending so that simply cloning sage results in the correct line ending for all files. See the following documentation for more information
https://code.visualstudio.com/docs/remote/troubleshooting#_resolving-git-line-ending-issues-in-containers-resulting-in-many-modified-files

Component: build

Author: Tobias Diez

Branch: 1f027c9

Reviewer: Matthias Koeppe

Issue created by migration from https://trac.sagemath.org/ticket/29733

[mkoeppe]

comment:2

Could you also take a look at the documentation that we have related to this in README.md? Does it need updating?

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

aba4268

Streamline readme based on changes

[sagetrac-git]

Changed commit from 4778e85 to aba4268

[tobiasdiez]

comment:4

Good point. I've changed the readme accordingly.

(Btw, the documentation at https://doc.sagemath.org/html/en/developer/walk_through.html is not really reflecting some of the recent changes to the readme.)

[mkoeppe]

comment:5

Thanks, I've opened #29784 for that.

[mkoeppe]

comment:6

Replying to @tobiasdiez:

Good point. I've changed the readme accordingly.

I think it's better to keep the --branch master in the documentation -- so that it becomes clear for beginners how to select a different branch...

[tobiasdiez]

comment:7

I probably miss something, but what's the purpose of the --branch master part? The clone command still fetches all branches so that changing a branch is a matter of git checkout <branch>. So why would you want to use the clone with a different branch?

But if you think it would be helpful, I'll readd this of course.

[mkoeppe]

comment:8

Replying to @tobiasdiez:

I probably miss something, but what's the purpose of the --branch master part?

Of course it's redundant but by including it, it is more obvious to beginning users what to change to get the "develop" branch. At this point they do not necessarily know about git, and I don't think the README is a place to educate them about it. Think of a user who used to unpack tarballs but is taking a tiny step into the scary git world.

[mkoeppe]

comment:9

In any case, removing it does not belong on this ticket.

[sagetrac-git]

Changed commit from aba4268 to 1f027c9

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

1f027c9

Readd branch statement to clone

[tobiasdiez]

comment:11

Ok, I've readded it.

[mkoeppe]

Reviewer: Matthias Koeppe

[tobiasdiez]

comment:13

Is there anything else to do from my side?

[fchapoton]

comment:14

no, just be patient

[vbraun]

Changed branch from u/gh-tobiasdiez/gitattributes to 1f027c9

[saraedum]

Changed commit from 1f027c9 to none

[saraedum]

comment:16

Could it be that this broke #30403?

[fchapoton]

comment:17

and this is also breaking some of the gitlab workers, maybe ?