> Hi. > > I'm sorry I'm in hurry as I must go for my ill daughter. So, in short: > > > Oh, I meant a replacement for join-lines-improved (I wrote: after the > > "feat/"), but I think it's OK. > > "feat" was just inspired from Vim's "FEAT_..." compiler switches. > > I vote for fix/fast_join. It is a fix, not a feature, I think. > Feature == new option or something like that. This is a fix of the slow > algorithm. I know that better word would be "an improvement" but in case I > have > just three words I must match in (fix, feat, dev), I vote for fix. > > Adding me to the project: my name at repo.cz is 'milan', so you can add me to > your project. Thank you. > > About other ideas: > > 1. your subscription is still missing in > http://repo.or.cz/r/vim_extended.git/README.html > > and it would be very nice to have your name there so a contact to the > maitainer will be well known. Do you agree? > > 2. what about other patches from > http://groups.google.com/group/vim_dev/web/vim-patches > > and the integration of them to vim_extended? > > 3. what about a promo of vim_extended at vim-patches page?
4. putting more git trees together: you can either pull from my git tree instead of me pushing to your one. This has an advantage that you have your git tree under control. 5. what about a cooperation with Christian and pul his git tree as vim_upstream? There is no dependency on svn, nice tags for vim versions are there... Would it be possible? 6. if you want to see more about git (in practice), there are documents describing a work of kernel hackers with git (sections for developers, subsystem maintainers etc.). For example this one looks good: http://www.kernel.org/pub/software/scm/git/docs/user-manual.html#sharing-development - just for inspiration what workflows are possible. Milan --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
