On the question of "Should .gitignore be in git": Today, I had to try to work with someone else's repository, and merge it into my stuff.
And, in the process, I realized that there are two types of files I don't want git to pay attention to. One is output files -- things that are generated during the build of a file. Those are things that change/update as the project updates, and should be tracked. The other is stuff from setting things up. These sit around, and should be ignored -- but they are local to my repository only, and won't be in someone else's. Things like "thoughts.txt", or "test.patch", or a source tarball. Or a second .gitignore file. Does it make sense to let git have two different gitignore files, so that one can be tracked, and the other not? Or am I doing something really wrong somehow? (The repository I was working with was only had one subdirectory and a readme file; all of the stuff that should be at the top level was missing, including a build.gradle file for controlling gradle, and probably other things as well. I'm going to try to reconstruct it.) --- Entertaining minecraft videos http://YouTube.com/keybounce -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
