On Thu, Mar 29, 2012 at 10:30 AM, Ben Fritz <[email protected]> wrote:
> > That's not github, by the way :-) > oops :) > It can be nice to pull from a real repository, but some people (me > included) would prefer to put experimental patches into a patch queue with > mq. I like this option better because Bram doesn't pull from clones, he > just uses the patches (or at least this is the case for the "official" > repository, obviously I don't know what his personal clones might look > like). So, if I pull a bunch of changes on the default branch into my > clone, that history never gets pulled in and either I will need to strip it > or let some extra head just dangle. > So if you want to commit to a clone, that's good, and you should share > it...but certainly continue posting patches on vim_dev. I wonder if there's > a good way to share patch queues related to a project? That might be an > even better way. Good point; I haven't used the mq extension before, so I'll go figure it out, along with its implied workflows. I'll probably have questions after that. ;) Thanks, -- Dave -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
