Hi, Peter Morgan wrote: > Best give I can give is to have the branches > - master = the latest stable release > - next = the next version and unstable
I am not that sure about the neccessity of the branches when moved to Git. They should probably be created only when the branch is found to be neccessary. They can mostly be local only. I suggest to use GitHub fork mechanism to keep the project responsibility firmly in Dimitri's hands (at least at the beginning). The Pull Request seems to be visible enough to decide whether to pull or not, or to use only some changes... However, I have only limited experience with Git, and I can be wrong ;) Petr ------------------------------------------------------------------------------ AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d _______________________________________________ Doxygen-users mailing list Doxygen-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/doxygen-users
