> > In the meantime I would like to know if there's a slick way to check svn > updates and runtime rsyncs against the list of 22 files the patch updates, > and re-apply the pieces of the patch affected? >
I wrote a patch that adds ":lscscope" to vim. It's in the TODO but hasn't been accepted yet (lack of testers? lack of visibility?). I use mercurial and mq to keep up to date with the latest vim and my patch, here's how: # One time only - create a local mercurial copy of the vim repository # and set it up for mq: $ svn co https://.../ vim7.2-svn $ hg convert vim7.2-svn vim7.2-hg $ cd vim7.2-hg $ hg qinit -c $ hg qnew lscscope $ vim .... (my stuff; in your case you'll do a patch -pN < ... ) $ hg qrefresh $ ./configure && make && make install # To keep up to date: # First clean up the sources if you built in that tree: # (careful with these two!) $ hg revert --all $ hg st -nu0 | xargs -0 rm # Temporarily unapply your patch $ hg qpop -a # sync up with the latest vim code $ (cd .. && hg convert vim7.2-svn vim7.2-hg) $ hg pull -u # Reapply your patch. This is where a merge may be required. $ hg qpush -a $ ./configure && ..... All this is mercurial centric and may not be what you're looking for. But it works for me.... Regards, Navdeep > I like this patch so much I am willing to examine every svn update and > runtime rsync against the list of files, and re-apply the pieces of the patch > that got overridden, but I can't help thinking there must be a better way. > > sc > > > --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
