<span id="result_box" class="" lang="en"><span title="Clique para mostrar traduções alternativas" class="hps">There will be</span> <span title="Clique para mostrar traduções alternativas" class="hps">an</span> <span title="Clique para mostrar traduções alternativas" class="hps">optional</span> <span title="Clique para mostrar traduções alternativas" class="hps">super</span><span title="Clique para mostrar traduções alternativas" class="atn">-</span><span class="" title="Clique para mostrar traduções alternativas">repository</span> <span title="Clique para mostrar traduções alternativas" class="hps">for</span> <span title="Clique para mostrar traduções alternativas" class="hps">kdeedu</span><span class="" title="Clique para mostrar traduções alternativas">? </span></span><span id="result_box" class="" lang="en"> <span title="Clique para mostrar traduções alternativas" class="hps">Something</span> <span title="Clique para mostrar traduções alternativas" class="hps">like</span> <span title="Clique para mostrar traduções alternativas" class="hps">KDE</span> <span title="Clique para mostrar traduções alternativas" class="hps">Graphics</span><span class="" title="Clique para mostrar traduções alternativas"> (<a href="https://projects.kde.org/projects/kde/kdegraphics/">https://projects.kde.org/projects/kde/kdegraphics/</a>) ?<br>
<br>Thank's,<br></span></span><br><div class="gmail_quote">2011/4/4 Sebastian Stein <span dir="ltr"><<a href="mailto:seb_stein@gmx.de">seb_stein@gmx.de</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Ian Monroe <<a href="mailto:ian@monroe.nu">ian@monroe.nu</a>> [110404 19:50]:<br>
<div class="im">> Enjoy. :)<br>
><br>
> The 4.6 branch and master will now be developed in Git. SVN is locked<br>
> read-only.<br>
<br>
</div>That is really great news!<br>
<br>
But now starts the trouble: How do we work with git? I have seen that there<br>
was a meeting about it, but as far as I can tell, there is no final outcome<br>
or even agreed workflow.<br>
<br>
I cloned kbruch, but now I wonder how to move forward? Is it expected that<br>
all feature development happens directly in master or shall we create<br>
branches? And if we use branches, are there any naming conventions?<br>
<br>
Is this document<br>
<br>
<a href="http://community.kde.org/20110213_GitWorkflowAgenda/StevesIdea" target="_blank">http://community.kde.org/20110213_GitWorkflowAgenda/StevesIdea</a><br>
<br>
the one to follow at the current point?<br>
<br>
<br>
Thanks in advance,<br>
<font color="#888888"><br>
Sebastian<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
kde-edu mailing list<br>
<a href="mailto:kde-edu@mail.kde.org">kde-edu@mail.kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kde-edu" target="_blank">https://mail.kde.org/mailman/listinfo/kde-edu</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Filipe Saraiva<br><a href="http://filipesaraiva.info/" target="_blank">http://filipesaraiva.info/</a><br>