Hi Petr, On May 20, 2013, at 17:06 , Petr Prikryl <[email protected]> wrote: >> [...] any tips are welcome ;-) > > I suggest to introduce the .gitignore file at the root level > with a directory that anyone can use for whatever. The reason > is that I would like to use some "private" subdirectory that > is near to doxygen's everything. > > Sure, I can make my own fork, my own .gitignore, and I can > secretly decide what the name of the directory is to be. > However, the pull request/merge would not be that easy in such case. > The goal is to keep the .gitignore public. Because of that, > the private subdirectory should be named publicly. > > It can be defined via prefix and the wildcard. I suggest > to put the following line to the .gitignore: > > __*/ > > i.e. two underscores, star, slash. This way, any directory > that starts with two underscores will be considered private. > > This way, developers will be free to create whatever private > subdirectory they like, wherever they like. > > The rule "the two-underscore prefix" is easy to explain.
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'll use this to exclude my own private stuff, and have a proper .gitignore that I can commit. Regards, Dimitri ------------------------------------------------------------------------------ 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
