On 03/13/2012 04:49 PM, Andreas Färber wrote: > > > > Not at all. I have a memory/core branch and a memory/urgent branch -- > > it's trivial to maintain them with git, and quite often I send a 1-patch > > pull request. There's no material difference between sending a patch > > and sending a pull request (except if you use git.kernel.org, ugh), and > > it does guarantee you priority handing. > > Actually there is: A trivial fix can be sent with a one-liner: > > $ git send-email HEAD^
Hey, I didn't know about this. Thanks. > whereas there is no matching command for sending a pull request. You > need to manage your own scripts that place git-pull-request output into > the cover letter. (And quite obviously you need a publicly available git > repository in the first place. Most of us do by now.) Implied by being a maintainer. So yes, it takes a little more effort to send a pull request. But it's still pretty easy. -- error compiling committee.c: too many arguments to function
