On Sunday, March 29, 2015 at 2:55:12 PM UTC+3, Guyz Zmolotov wrote: > On Sun, Mar 29, 2015 at 04:04:23AM -0700, ZyX wrote: > > On Sunday, March 29, 2015 at 1:57:31 PM UTC+3, Fredrik Gustafsson wrote: > > > On Sun, Mar 29, 2015 at 03:55:55AM -0700, ZyX wrote: > > > > NeoVim project tried to do this and found it non-comfortable to keep > > > > them in > > > > sync (I mean, any contributor which needs to change both code and > > > > documentation needs to create two separate pull requests). > > > > > > > > Thus if runtime will be separated at least runtime/doc should be kept > > > > in main > > > > repository. Submodules suggested later cannot solve this issue at all. > > > I fail to understand why submodules cannot solve this problem. Would you > > > care to elaborate? > > Please show me an example of the PR which will update *both* the main > > repository and the submodule. If this is possible then submodules can solve > > this problem, but I have never seen this functionality. > > then use git subtree. > > http://git-scm.com/book/en/v1/Git-Tools-Subtree-Merging > https://medium.com/@v/git-subtrees-a-tutorial-6ff568381844 > http://blogs.atlassian.com/2013/05/alternatives-to-git-submodule-git-subtree/ > https://help.github.com/articles/about-git-subtree-merges/ > > HTH, > > -- > Guyzmo
This still has downsides comparing to single repository: 1. PRs to runtime will now be scattered between /runtime/ repository and / repository. 2. Duplicate history entries in /runtime/ and /. 3. Requirement to do two-way synchronization between / and /runtime/. a. Still any change to /runtime/ needs corresponding change to /. b. Yet changes to / may need to be pushed to /runtime/. Note that both solutions (submodules and subtrees) only make sense if 1. Bram is going to give more people RW permissions for /runtime/ repository. 2. Somebody will set up a hook which will do the synchronization. Have not yet heard about the 1 and it is the only thing which may justify the separation. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
