Should maiko, notecards, loops, test have a .gitattributes, and what should it state?

[MattHeffron]

Should medley's sibling repos (esp. maybe soon to be submodules) have .gitattributes files?
If so, what should they state?
The maiko, loops and test repos don't have that file.
notecards does, but only designates *.notefile (UPPER and lower case) as -crlf.
(This seems incorrect since a .notefile appears to contain binary information!)

The medley repo .gitattributes file marks *.tedit, *.lcom, *.sketch, and *.dfasl all (both cases) as binary. I'm surprised that the lack of these being marked as binary in other repos hasn't broken things for someone.
I don't know what the file should contain for the maiko repo.

[nbriggs]

For maiko, every file checked in is text, and every file is Unix LF end-of-line convention except for bin/makefile-dos, which is DOS CRLF convention. I'm not sure what the .gitattributes should look like to just maintain all the files as-is. I think modern Windows systems can cope with LF eol convention?

[MattHeffron]

Without a .gitattributes file, the treatment of files depends on the settings in the local, global, and system git config files.
The local (.git/config) file is not defined by the repository on github. (I.e., it isn't automatically shared.)
If a user's global or system config don't set it correctly for the necessary behavior of the specific repo, it needs to be set by each user.
maiko doesn't have a .gitattributes and its eol handling (core.autocrlf) cannot be pre-specified in the local config file, so it is sort of a gamble that it will be correct for any given user.
If every file in the maiko repo is text and, with the noted exception, should have lf as eol, then I think from the git documentation, we'd want a .gitattributes of:

bin/makefile-dos eol=crlf     # the one exception to lf eol
* eol=lf                                  # everything else

Does this look right?

[fghalasz]

Added appropriate .gitattributes to Notecards repo - checked into main.