GSoC'20 progress : Phase I related

[Prasun Kumar]

Hi Ralf,
I have opened a merge request for the bug.
https://sourceforge.net/p/ktoblzcheck/code/merge-requests/10/

Before opening a merge request for the commits, I would like to remind you
that I have
still not dealt with the methods of public API which do not make sense any
more. As you
suggested to not use the DEPRECATED macro, I could not find any suitable
thing to do with
them. Please advise if I should do anything regarding this.

You may run uncrustify.sh [1] from the source dir before opening the
> merge request and check all commit messages against spelling errors.
>

Silly question, but could you suggest a good commit message after the
changes by code beautifier?

Meanwhile, if you could give some pointers regarding the support of
additional countries,
I could start planning for it according to my timeline.

Thanks.
Prasun

On Fri, 10 Jul 2020 at 13:47, Ralf Habacker <ralf.habacker at freenet.de>
wrote:

> Am 06.07.20 um 21:30 schrieb Prasun Kumar:
> Hi Prasun,
>
> > BTW: You can read the progress reports at my blog:
> > https://prasunka.github.io/tag/gsoc/
>
> Nice. To complete the first task to 100% the changes should be merged
> into the master branch of the ktoblzcheck project by opening a merge
> request. After this merge a new release can be make with this feature
> included.
>
> You may run uncrustify.sh [1] from the source dir before opening the
> merge request and check all commit messages against spelling errors.
>
> After opening the merge request, the mentors are going to review the
> changes and are merging the patches, if no issues will be found.
>
> [1] Unfortunally the mentioned script contains a bug
> (https://sourceforge.net/p/ktoblzcheck/bugs/5/), which need to be fixed
> first.
>
> Ralf
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-finance-apps/attachments/20200711/07971f6e/attachment.htm>