On Fri, Jul 4, 2008 at 2:12 AM, Markus Heidelberg <[EMAIL PROTECTED]> wrote: >> Keep in mind that: >> - this is not upstream of course > > With the only difference that it's inofficial, right?
exactly! the purpose is to keep an updated version, as accurate as cvs/svn/tarballs+patches with correct dates and ownership. > >> - each release has its own branch (master=7.1) >> - this will not include the betas, only pristine/official releases and >> the usual set of patches from Bram > > What speaks against a branch for 7.2a? The purpose was for released versions if possible. I guess I can create (soon) a branch for 7.2a. I'll see if I get good internet access in the next 4 weeks or not (holidays). > >> Here's the nice bits: >> - Git users should be able to use this easily to rebase partially >> bitrotted patches >> - we should be able to maintain specific patches using branches > > Do you have the recently started "Vim Patches Project" discussion in mind? yes, that was my point. you could keep this "vim patches project" in sync as a branch and update it accordingly. > > If this tree would be kept up-to-date to some extent, I'd like use it in favor > of the subversion access. But of course there should be a branch for the head > of development (7.2a). I'll keep it up to date (maybe not for the next 4 weeks at least). I'll try to get this 7.2a branch started soon. (this is git: I should be able to do it on the plane :-)) -- Christian -- http://detaolb.sourceforge.net/, a linux distribution for Qemu with Git inside ! --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
