> On Thursday, July 28, 2011 12:28:52 AM UTC+2, JohnBeckett wrote:
> > There is one more wet blanket you need to be aware of.
>
> > It may be the case that the complexity would rule out acceptance
> > of the proposed changes since adding stuff to the source makes
> > future maintenance and development more difficult.
>
> While not my first choice I could maintain this as a set of patches against
> the official release of vim. But obviously I would much prefer it this
> became part of the official vim! :)
>
Rather than that, I'd suggest making a clone of the Vim repository on
google code in Mercurial, and making/maintaining your changes there.
You can keep the close on google code associated with the Vim
repository, right from code.google.com/p/vim. Or, you could make a new
project on google code or bitbucket which is actually a clone but not
obviously associated.
Then collaborative development can occur easier as well.
--
You received this message from the "vim_use" 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
No comments:
Post a Comment