Ben Schmidt wrote: > On 30/01/11 11:05 AM, Marc Weber wrote: > > Does the current vim.sf.net page tell about existing repositories where > > vim patches mature ? > > > > If if they are never merged upstream it would be nice to have a local > > place to share them. > > > > I know about a git repository which collects many of them. > > Mmm. But last I heard it was kinda about to explode? Or are we talking > about different things? Here's an edited version of an email I sent > recently on this subject: > > I notice on the page > http://groups.google.com/group/vim_dev/web/vim-patches > at the moment there is a THIS IS GOING TO BREAK SOON notice from Google. > Is there any replacement page somewhere that takes over the role of this > page, or plans for one? > > Also, I just went to endeavour to pick up the current variable tabstops > patch, which I believe is in vim_extended: > http://repo.or.cz/w/vim_extended.git > > I notice there is mention there that this repository is to be > discontinued. Are there plans for a replacement for this? > > I personally think a Mercurial repository based on Vim's official > Mercurial repo would make most sense. > > But git also works, though, again, I think it should, via hg-git, be > based on Vim's official repository. > > Obviously someone needs to maintain it, pulling from the Vim repo > periodically, and reapplying patches, and coordinating with patch > authors when there are conflicts which aren't easy to resolve, etc. > > > How do you think about adding a description of this on the download or > > development page on vim.sf.net? > > I think that would be a good idea. The beauty of DVCS is that anyone can > publish a repo, and if done right, they all link to the official Vim > repo, too, and can be combined and merged by anyone as they like. The > difficulty is knowing where to find these repos, and so something on the > Vim page would be great, whether to a combined repo like vim_extended, > or a longer list of other contributed repos, or a searchable database a > bit like the vim scripts (though hopefully better, and by the way, I > like a bunch of the proposals that you sent a while ago for improving > the vim scripts database).
I think every script could have a repository associated with it. If we allow uploading patches and mark them as such it's mainly a matter of adding a new script type. It's easier to explain that a script can also be a patch than to start a whole new section which would be mostly the same. -- Keep America beautiful. Swallow your beer cans. /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- 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
