On Monday, May 21, 2012 2:11:13 AM UTC-5, JohnBeckett wrote: > > Ben Fritz has pointed out that a second independent repo could > be created (vim-runtime-dev?) where any maintainer or other > interested party could be given access for "hg push". Then > reviewers could pull changes into the stable vim-runtime repo. > Ben mentioned that if a Google code repo is a clone of another, > the clone cannot have a second committer. So, each repo would > have to be fully independent. A second repo could happen later, > when there was a demonstrated need. >
Perhaps I was not clear. There can be any number people with "push" access to a project. You can see contributors listed under the "members" area on the project home page. What you cannot have more than one committer to, is the server-side clones listed on the same project. These are the clones created if you click the "source" tab on the google code page, then hit the "create a clone" button. You can see a few dozen clones on the Vim project page, on the "source" tab, under "Clones". These clones can only have a single contributor. If the runtime repository was a full clone of the Vim repository, it would make sense to have it listed under this "Clones" area...except that these clones only get a single committer, so that's not really an option. It would be easy enough to create a new project on Google Code which is really a clone of the Vim repository, but the two projects would not (as far as I know, and as far as Google Code is concerned) be linked in any way. -- 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
