merge cpplint forks

[tkruse]

Hello,

I also maintain a cpplint fork at
https://github.com/tkruse/cpplint
and I release cpplint to pypi.

If you like, we could try merging both repositories. Or I can try to grab your patches. Have you submitted them to the issue tracker yet (https://code.google.com/p/google-styleguide/issues/list)?

[tkruse]

Actually I just went ahead and created an ostricher branch in my repo with your commits:
https://github.com/tkruse/cpplint/tree/ostricher
not sure how to proceed with this, in particular with nitpick and the additional option.
But if you'd like, you could delete your repo and fork mine with your changes, that way it will be easier in the future to exchange patches.

[itamaro]

Hi,
cool.
I planned to submit my cpplint changes to the issue tracker, but didn't get
to it yet...
I thought I'd leave nitpick out of it, as it's an independent optional
tool, with no formal support.
Also not sure how to proceed. If you want to adopt my cpplint changes, I
can fork your repo and maintain my nitpick on top of it. WDYT?

On Sun Jan 04 2015 at 7:33:15 PM Thibault Kruse notifications@github.com
wrote:

Actually I just went ahead and created an ostricher branch in my repo with
your commits:
https://github.com/tkruse/cpplint/tree/ostricher
not sure how to proceed with this, in particular with nitpick and the
additional option.
But if you'd like, you could delete your repo and fork mine with your
changes, that way it will be easier in the future to exchange patches.

—
Reply to this email directly or view it on GitHub
#1 (comment).

[tkruse]

You can fork my repo in any case. That will make it easier for me to pick up changes from you. And of course you can add nitpick or other things on top of that in your own fork. If you can, make separate commits for nitpick and cpplint stuff, as you already did, that makes it easier for me.

I tried to structure my repo so that merging in new changes from svn is easiest. It is not a nice structure for adding more scripts, but I can live with that. I also considered cloning the whole styleguide root, but that also did not seem right.

I cannot tell yet how mature and useful nitpick is, so I will not include it in the release of cppclean for now. Once you think it is ready for a larger audience, maybe you can rename it to start with cpp. THen it could be included either in cpplint, or as an independent pypi package depending on cpplint.