Hi Maxim,
On Oct 13, 7:03 pm, Maxim Perenesenko <
171...@gmail.com> wrote:
>
> There are a lot of minor warnings during building current version of
> memcache++, like the attached below.
>
Oh boy, you're right. I haven't been testing with -Wall, I should do
that from now on.
> As the library is a header-only, any cpp file, which uses it,
> generates a lot of output and locating real errors and warnings is
> becoming a very hard and tedious task.
>
> BTW, these warnings are very easy to fix. I would fix them easy.
> However, I am not very familiar with git and do not know formal
> procedure of committing into the project as well.
>
It's really very easy, you can go to
http://github.com/mikhailberis/memcachepp
and create a fork. This requires that you have a GitHub account set up
correctly.
Once you have your fork of the project, you can clone it to your local
machine and start hacking on it locally. Once you've committed your
changes locally, you can then push your changes to your fork in
GitHub. When you're ready to have your changes merged to my
repository, you can go ahead and submit a pull request.
You can read more about forking here:
http://help.github.com/forking
And submitting pull requests here:
http://help.github.com/pull-requests
Thanks for trying it out -- let me know how things go.
[snip warnings output]
--
Dean Michael Berris
deanberris.com