> > On one hand, we all agree that .gitignore and .gitattributes (and so > > on) are useful when building a project (prior to the final packaging). > > The primary purpose of those files are git commands. > Having them evaluated by other tools is kind of unexpected (at least for > me)...
Well, giving it a second thought, I have to agree that the primary purpose of those files are git commands, and it might not be a good idea to depend on them to be able to build the project. OTOH, if *source-release.zip files act as just the zip source distribution of the repository (similar to doing the "Download ZIP" from GitHub), then it makes sense that it includes those files, but it also means that every other file should also be included (eg. .cvsignore), but if the intention of the *source-release.zip files is to have a "clean" distribution of the source distribution then yes I agree that they should be filtered. In the end, it might be a matter of preference and/or configuration, Apache Calcite uses .gitattribute in the build, but many others might not need them, so a configurable option make sense here. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
