2017-02-19 11:55 -0700, Ryan May <rmay31 at gmail.com>:
Thanks for the patch. Would it be possible for you to submit this as a Pull
Request on GitHub:
Hi Ryan,
I would prefer not to do it, because I would have to configure GitHub
account for that and I see no benefit to do that ATM. (Considering the
triviality of the patch.)
I decided to go the "patch over email" way, because it is documented in
the Dev Guide [1] and it's simpler and easier for me than PR.
It's also easy and simple for a commiter to apply the patch with:
git am name-of-the.patch
Please tell me if there are any problems with the pathc.
It's fine--PR is just easier for devs because it doesn't require anything
except the web interface. Also, all additions to Matplotlib have to go
through a PR at some point.
On Sun, Feb 19, 2017 at 12:44 PM, <aufc at cock.li> wrote:
2017-02-19 11:55 -0700, Ryan May <rmay31 at gmail.com>:
> Thanks for the patch. Would it be possible for you to submit this as a
Pull
> Request on GitHub:
Hi Ryan,
I would prefer not to do it, because I would have to configure GitHub
account for that and I see no benefit to do that ATM. (Considering the
triviality of the patch.)
I decided to go the "patch over email" way, because it is documented in
the Dev Guide [1] and it's simpler and easier for me than PR.
It's also easy and simple for a commiter to apply the patch with:
git am name-of-the.patch
Please tell me if there are any problems with the pathc.
2017-02-20 12:35 -0700, Ryan May <rmay31 at gmail.com>:
It's fine--PR is just easier for devs because it doesn't require anything
except the web interface. Also, all additions to Matplotlib have to go
through a PR at some point.