Now I see. I'm not sure what's the best way of doing it either, but your idea sounds good. Did you investigate the possibility of faking the commit dates?
Seeing as Git is a distributed system, I don't see why you shouldn't be able to set arbitrary commit dates, with a custom rebasing script. At worst, you'll have to compile a custom git, hacking around the getdate() call, to accept a commandline parameter with the date to use. Then, after the macvim patches are rebased on top of an old vim- extended commit, automatic merges (both ways) will be possible. The only real downside is that all commits would change hash. In my case, I'll try to see if vim_extended tracks vim trunk someway, then I'll format a patch from the branch I'm interested in and apply it to macvim. That should be smoother. Tobia --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_mac" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
