Richard Hartmann, 22.12.2008:
> 
> On Mon, Dec 22, 2008 at 14:31, Markus Heidelberg
> <[email protected]> wrote:
> 
> > Richard, I hope you can understand that I haven't yet tackled the Readme
> > file. I haven't forgotten it.
> 
> Sure, no worries, I know how it is ;)
> There are a few new & interesting patches listed on Josh's site, maybe
> you could merge them, once you have more free time?

I wanted to apply the patches "Unified colors for consistent color
schemes", but the runtime.diff was really ugly: it contained 3 *.orig
files and an older ctermrgb-runtime.diff itself. I wasn't keen on doing
it anymore.
And I want to try the "Correctly indent wrapped lines" patch, where I
probably also have personal interest in. But I didn't get round to it so
far.

I'd really like the authors of these patches to send me up-to-date
patches that can be applied without problems, if they are interested to
have it in vim_extended.

> I plan on spending a lot of time away from computers over christmas,

Me too, but it didn't work for now :)

> but after than, if you give me commit access, I can try to help merge
> new patchsets and the README into vim_extended so you have less
> work.

You already have commit access, it's distributed, just let me pull :)
But giving you push access is fine with me. We just have to write some
guidelines before it to keep the repository clean and consistent.

The final README I'd like to commit myself because of some git specific
stuff. But I also wonder if we should put it into a 'stuff' branch as I
did it in vim_mainline.git (not yet the README file)? Maybe a new branch
would rather be recognized than yet another README_*.txt file beside
others. If you want to have the files from the 'stuff' branch in your
custom branch, you can just merge it, if it doesn't contain conflicting
paths.

Markus


--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Reply via email to