-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 28.04.2014 17:04, JonY wrote: > On 4/28/2014 19:53, Ruben Van Boxem wrote: >> Different repositories may sound like a nice idea, but keeping them in >> sync can be a pain, depending on the complexity of the subprojects. I >> believe stuff like ironcrate, winpthreads and perhaps the >> mingw-w64-tools folder deserve their own repo, as they are very seperate >> from the headers+crt. These latter two I'd suggest to keep together, as >> that will reduce the chances of wrong versions being used together and >> allow 1 commit to change both to keep them aligned without any hassle. >> In contrast, I would try to move away from a seperate "experimental" >> directory, and instead inject these changes into a branch (or several, >> so that each finished feature can be merged easily). Branches and >> merging are the git way, and rebasing allows for clean merges. >> > > For ease of migration, every module in trunk would go into the same repo, > so that would include winpthreads and mingw-w64-tools. I'm not sure if we > can "exclude" files from the import unless we want to completely break > apart trunk into components. However, I am also trying to avoid too many > separate repos and git submodules. > > Right now, I am thinking of splitting it 3 ways, the mingw-w64 proper > (with anything from experimental if applicable), web, and experimental (if > it actually justifies a separate repo, otherwise, it might be archived and > left as is on SVN).
My experience so far: 1) When i build gcc, i often need to build mingw-w64-headers, mingw-w64-crt and winpthreads not together, but separately, at different points of time. To this end i'm svn-checkouting from a subdirectory to get only one of the three. I don't remember whether git has that ability; possibly not. If that is the case, these may need to go into separate repos (possibly submodules?). 2) The git branches are for "branching out" from the main development line (and merging back at some later point), not for completely separate stuff. If you keep completely different stuff in different branches, switching branches (which usually takes less than a second) will take a long time (depending on the size, up to 10 seconds or more). The svn "branches" are more like git "repos" - completely independent, they just "live together" :) - -- O< ascii ribbon - stop html email! - www.asciiribbon.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (MingW32) iQEcBAEBAgAGBQJTXl/DAAoJEOs4Jb6SI2Cw+LoH/jeC5Gu884aNkcEk1k19/q7+ kVmM8Sb0b2WW+v063xb7ZqcWxtQUf/egXaRUFQJTgYYsOKPF+5SeJWpxyuGpjsjN 2mLzo2LtygqaIl/XI+rtGO2LipJW3d7Uo1Puq1oWctcH3LG1QQJLvkOqQLJzwnpF M7niIwtspZpOtRHGPEQAespVpY3mH2hkvRd6tPAj51w1Ix/d4OwfAjsW80EGJIwC oT/qvM4gAADIGz11zmIzplGCOmOvsi8JENEgQB1szKQ2vih8bFwaOhM433a38zCZ ehx4JIasVL13TtJRliSSgEHCh6kKJGD+V6+nOyD5TNrCfL9NIRV7YWbyQu9sC78= =Qy6h -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
