On Fri, Jan 23, 2009 at 12:29 AM, Markus Heidelberg <markus.heidelb...@web.de> wrote: >> 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? > > No, it wouldn't. > It looks nice at first sight, but it isn't really useful for > development. Look at the branches, they each have their own root, they > don't have any relation to each other. With Vim 7.3, the master branch > will be rewritten from scratch. You can't merge and forward-port the > feature branches to the next minor release. In fact you'd end up with a > rebase of all your branches as well. >
it's not a bug, it's a feature (tm). As you mentioned later in this thread, you're not familiar with vim development from the start (neither am I: I missed the pre-3.0 days, as I did not have an atari). Maybe Bram should comment on this. seriously, each branch having its own root was my way of representing that each vim main release usually has too many changes with the previous one. I can change that if needed: how would you like my repo to look like in terms of branches ? I just got a patch from the git mailing list which will make the maintenance of my vim repo much easier :) So I'm about to rip off the current repo on github and I'm willing to include changes/suggestions *now*. Let me know... ;-) About your last point (not being able to backport), it's not true: you can still cherry-pick :) -- 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 -~----------~----~----~----~------~----~------~--~---
