On Thu, Jul 24, 2014 at 2:12 PM, Darshit Shah <[email protected]> wrote: > Probably. I simply redirected the output of 'git status' and manually sorted > them into the directories.
Split them in multiple .gitignore (per directory) is good. A single large .gitignore may slow things down. See http://article.gmane.org/gmane.comp.version-control.git/194294 > However why is a slash prefix a good idea? It gives git a hint that these entries only apply to top-level directory, so git can ignore them when examining subdirectories > > — > Sent from Mailbox > > On Thu, Jul 24, 2014 at 12:52 AM, Ángel González <[email protected]> > wrote: > >> Darshit Shah wrote: >>> Hi, >>> >>> When building the repository sources, a large number of files are >>> autogenerated and hence are not version controlled in git. >>> However, all these files pollute the output of commands like `git >>> status`. The only way around it is to place all the autogenerated >>> files in a single .gitignore file and share it with the repository >>> itself. >>> >>> I've compiled a .gitignore that can be used in Wget's repository. This >>> file ignores all the autogenerated files due to bootstrap, configure, >>> make and make check. >>> On top of it, I've also ignored some extra files like tags and >>> cscope.out which I assume a lot of developers are probably using. I've >>> attached the file for everyone's convenience here. Maybe we can ship >>> this file with the sources itself? >> +1 >> But I would prefix with a slash the files in the Project Root. -- Duy
