Richard Hartmann, 08.12.2008: > > On Mon, Dec 8, 2008 at 01:10, Markus Heidelberg > <[EMAIL PROTECTED]> wrote: > > >> Markus, please put the attached file into the git repo. > > > > In which branch, master? > > Yes. That way, everyone will be able to see the README.
I've got it. I will put a README file into the master branch and replace the usage part in gitweb with a hyperlink to that file. > > But I'd like to keep it short, forgoing all the things that aren't > > special for vim_extended like details in configuring Vim and setting up > > git. There is already enough documentation out there, a Vim novice won't > > use vim_extended anyway, a git novice though. > > Well, a git novice might not know about the color.ui option and it really > _does_ make working with git easier. I have no problem dumping it, though. Correct, it does make _working_ easier. And to _work_ with git, you have to read the docs anyway. The implicitly necessary actions (clone, merge, pull) should suffice. > > I wonder if it is better to activate the features by default. The Lua > > interface for example. I think it is, nobody wants to merge the lua > > branch for not using it, do you agree? > > Why not offer a mergeall branch or something? Personally, I > cherry-pick the interesting (to me) stuff, but others might prefer > to just build the whole beast. > We would then have three parts in the docs: Vanilla, Cherry & All. The master branch is the mergeall branch or do I misunderstand you? Markus --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
