For the non-private purpose, there probably still is the need for .gitignore files (at least related to compilation for Windows) to exclude the generated files (also the VERSION file) -- probably at the root level:
bin/Debug/ bin/Debug64/ bin/Release/ bin/Release64/ VERSION There also should be winbuild/.gitignore file with at least the following: Debug/ Debug64/ Release/ Release64/ Doxygen.ncb Doxygen.suo *.user And there also should be src/.gitignore to exclude the files generated from lex sources. Dimitri wrote: > Petr Prikryl wrote: > > I suggest to introduce the .gitignore file [...] > > to use some "private" subdirectory [...] __*/ > > i.e. two underscores, star, slash. This way, any directory that > > starts with two underscores will be considered private. > > I just found this > http://365git.tumblr.com/post/519016351/three-ways-of-excluding-files > using the 3rd method (excludesfile in .gitconfig) you can add > additional stuff to ignore. Seems like a better approach for private > stuff. I agree this is better approach for private directories. I am going to use the 2nd metod (.git/info/excludes) for some reason. Still learning ;) Regards, Petr ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may _______________________________________________ Doxygen-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/doxygen-develop
