[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-finance-apps
Subject: Re: GSoC '21 KMyMoney : I am stuck.
From: Suraj Kumar Mahto <suraj.mahto49 () gmail ! com>
Date: 2021-06-25 21:57:28
Message-ID: CAEDvbQBsxSY7JR2M1jk0pkyr=3U0WdQzLaa=WEMXgq4zxAoJFA () mail ! gmail ! com
[Download RAW message or body]
Hello, I wrote the blog post of Week 1 and 2 yesterday:
https://suraj-sloth.github.io/2021/06/25/gsoc21-week1-2.html
I have planned to work more considering that my pace is slow for the
project as of now and I am lagging behind.
Regards
Suraj Kumar Mahto
On Fri, Jun 25, 2021 at 9:53 PM Thomas Baumgart <thb@net-bembel.de> wrote:
> Hi,
>
> On Freitag, 25. Juni 2021 00:00:33 CEST Suraj Kumar Mahto wrote:
>
> > Hello,
> > I think I have fixed the crash bug. Thank you very much for the help. I
> did
> > the changes in kmymoney repo only and I have pushed those changes to
> > https://invent.kde.org/surajsloth/kmymoney/-/tree/gsoc21 . I have pushed
> > the changes. Although the new quote button is disabled. That is needed to
> > be figured out.
>
> I am sure, that you can figure that out. If you have trouble, I can also
> take a look at it and give you some guidance.
>
> > My forked changes(gsoc21 branch) can be merged into gsoc21 branch of the
> > upstream repo. This way I am dealing with a forked repo also and my
> entire
> > work is there is a separate branch of upstream repo. What do you think
> > about this?
>
> Doing the work in your fork is just fine. Keep it in the fork and once
> you're done, we can pull it into the KMyMoney main repo with a merge
> request.
> There is no need to keep a gsoc21 branch in the KMyMoney repo in sync.
>
> I have a clone of your forked repo here on my system where I can checkout
> your current state from the fork and help you out if needed. It is very
> helpful if you sync with KMyMoney master every now and then as you did
> today.
>
> --
>
> Regards
>
> Thomas Baumgart
>
> https://www.signal.org/ Signal, the better WhatsApp
> -------------------------------------------------------------
> The spread of unverified or deliberately falsified information from
> gutter-level sources in the wake of crises, aided by venues like Google
> and Twitter, has become a real problem with real consequences. -- Tom McKay
> -------------------------------------------------------------
>
[Attachment #3 (text/html)]
<div dir="ltr"><div><div><div>Hello, I wrote the blog post of Week 1 and 2 yesterday: \
<a href="https://suraj-sloth.github.io/2021/06/25/gsoc21-week1-2.html">https://suraj-sloth.github.io/2021/06/25/gsoc21-week1-2.html</a><br><br></div>I \
have planned to work more considering that my pace is slow for the project as of now \
and I am lagging behind.<br><br></div>Regards<br></div>Suraj Kumar \
Mahto<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, \
Jun 25, 2021 at 9:53 PM Thomas Baumgart <<a \
href="mailto:thb@net-bembel.de">thb@net-bembel.de</a>> wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">Hi,<br> <br>
On Freitag, 25. Juni 2021 00:00:33 CEST Suraj Kumar Mahto wrote:<br>
<br>
> Hello,<br>
> I think I have fixed the crash bug. Thank you very much for the help. I did<br>
> the changes in kmymoney repo only and I have pushed those changes to<br>
> <a href="https://invent.kde.org/surajsloth/kmymoney/-/tree/gsoc21" \
rel="noreferrer" target="_blank">https://invent.kde.org/surajsloth/kmymoney/-/tree/gsoc21</a> \
. I have pushed<br> > the changes. Although the new quote button is disabled. That \
is needed to<br> > be figured out.<br>
<br>
I am sure, that you can figure that out. If you have trouble, I can also<br>
take a look at it and give you some guidance.<br>
<br>
> My forked changes(gsoc21 branch) can be merged into gsoc21 branch of the<br>
> upstream repo. This way I am dealing with a forked repo also and my entire<br>
> work is there is a separate branch of upstream repo. What do you think<br>
> about this?<br>
<br>
Doing the work in your fork is just fine. Keep it in the fork and once<br>
you're done, we can pull it into the KMyMoney main repo with a merge request.<br>
There is no need to keep a gsoc21 branch in the KMyMoney repo in sync.<br>
<br>
I have a clone of your forked repo here on my system where I can checkout<br>
your current state from the fork and help you out if needed. It is very<br>
helpful if you sync with KMyMoney master every now and then as you did<br>
today.<br>
<br>
-- <br>
<br>
Regards<br>
<br>
Thomas Baumgart<br>
<br>
<a href="https://www.signal.org/" rel="noreferrer" \
target="_blank">https://www.signal.org/</a> Signal, the \
better WhatsApp<br>
-------------------------------------------------------------<br>
The spread of unverified or deliberately falsified information from<br>
gutter-level sources in the wake of crises, aided by venues like Google<br>
and Twitter, has become a real problem with real consequences. -- Tom McKay<br>
-------------------------------------------------------------<br>
</blockquote></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic