https://d.puremagic.com/issues/show_bug.cgi?id=11792
--- Comment #4 from Mathias LANG <[email protected]> 2014-01-06 08:01:51 PST --- (In reply to comment #3) > This sounds similar to my D.git experiment: > > http://forum.dlang.org/post/[email protected] > > The repository is automatically generated from the component repos' histories > and periodically updated (currently hourly). > I am getting 404 on the mentioned repository (but D-dot-git works). > > 1) Starting from 1.8.2, git can track a branch, not only a commit. > > That would preclude importing history, and would make it unusable for > regression testing. > Submodules are not really meant for importing history. Actually, looking at the man page kind of advise you against doing this: https://www.kernel.org/pub/software/scm/git/docs/git-submodule.html (2nd paragraph of the description). > > We should also take care not to accept a PR with a modif to .gitmodules > > unless it's a stable version update. > > Why would anyone send a pull request to the meta repository, unless it's e.g. > to add/fix makefiles? In my approach, that would be to update the pointed commit (you still have a pointed commit with --remote). Now, how do we handle testing PR that require Makefiles changes ? If I do a PR to Phobos, and one to the superproject which modify Makefiles, how does the auto-tester will possibly handle it ? -- Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------
