<div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"><br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On 1 September 2015 at 02:14, Yue Liu <span dir="ltr"><<a href="mailto:yue.liu@mail.com" target="_blank">yue.liu@mail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span><p dir="ltr"><br>
On Aug 31, 2015 2:50 AM, "Dmitry Kazakov" <<a href="mailto:dimula73@gmail.com" target="_blank">dimula73@gmail.com</a>> wrote:<br>
><br>
><br>
>>> 1) I'm ok with forking Krita repository. We already depend from quite few libraries from calligra libs. That is mostly, KoCanvasBase, KoDocumentBase, flake and pigment.From all four only pigment looks<br>
>>> reusable enough for me to have a separate repo. In our code we hack quite a lot to adapt flake and document classes for our needs.<br>
>>><br>
>>> 2) One more benefit of forking to another repository would be that the size of the repo would become lower (correct me if I'm wrong). Since "Krita for Cats" manual is still semi-official way of building<br>
>>> Krita on some platforms this is really crucial for many users. Quite a lot of people still have GPRS or limited internet, so downloading 700MiB just to try Krita *is* a barrier. Another problem is<br>
>>> translators. Basically, they need to have a full source tree around to be able to check where the string comes from.<br>
>><br>
>><br>
>> The repo size is one reason I'm actually considering to drop all<br>
>> history. Create a fresh new repo with cleaned-up code only and start<br>
>> again from commit 0. I know we check history a lot, but that history is<br>
>> the history of Krita up to Krita 2.9.x, which is in the calligra repo.<br>
><br>
><br>
> This will make our life really hard :(<br>
> </p>
</span><p dir="ltr">For git there is a way to move files from one repo to another repo while keeping history to only those files. You can do that for Krita split, first create a branch to strip off office apps code, then create an empty krita repo, then move all files and their history to the new repo.</p>
<p dir="ltr">This way you make repo smaller but still have krita history.</p></blockquote><div><br><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">Yes, please see for example:</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small;display:inline"><a href="https://community.kde.org/Kexi/Porting_to_Qt%26KF_5#Git_surgery" target="_blank">https://community.kde.org/Kexi/Porting_to_Qt%26KF_5#Git_surgery</a></div> <br><br><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">I did so with 3 repos splitted from calligra, 11 years of history. Every file starts in src/*, even those from 2004. Even tags can be kept. Of course prior revisions won't build; for buildable we have frameworks and calligra/*.* branches of (current) calligra.git.<br><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">I am offering technical help here.<br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"><br>BTW, If we cut of, say, prior Krita history from calligra.git, it won't be the original calligra.git anymore that people want to reference to see the pre-september-2015 history. <br>We'd need a name for the original (large) calligra git repo with all the apps.<br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">calligra2-history.git? Simply calligra2.git sounds misleading.<br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"></div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span><font color="#888888">
</font></span><p dir="ltr"><span><font color="#888888">> -- <br>
> Dmitry Kazakov</font></span><span><br>
><br>
> _______________________________________________<br>
> calligra-devel mailing list<br>
> <a href="mailto:calligra-devel@kde.org" target="_blank">calligra-devel@kde.org</a><br>
> <a href="https://mail.kde.org/mailman/listinfo/calligra-devel" target="_blank">https://mail.kde.org/mailman/listinfo/calligra-devel</a><br>
><br>
</span></p>
<br>_______________________________________________<br>
calligra-devel mailing list<br>
<a href="mailto:calligra-devel@kde.org" target="_blank">calligra-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/calligra-devel" rel="noreferrer" target="_blank">https://mail.kde.org/mailman/listinfo/calligra-devel</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div>regards, Jaroslaw Staniek<br><br>KDE:<br>: A world-wide network of software engineers, artists, writers, translators<br>: and facilitators committed to Free Software development - <a href="http://kde.org" target="_blank">http://kde.org</a><br>Calligra Suite:<br>: A graphic art and office suite - <a href="http://calligra.org" target="_blank">http://calligra.org</a><br>Kexi:<br>: A visual database apps builder - <a href="http://calligra.org/kexi" target="_blank">http://calligra.org/kexi</a><br>Qt Certified Specialist:<br>: <a href="http://www.linkedin.com/in/jstaniek" target="_blank">http://www.linkedin.com/in/jstaniek</a></div>
</div></div>