<div class="gmail_quote">On Tue, Nov 23, 2010 at 9:23 AM, Andreas Pakulat <span dir="ltr"><<a href="mailto:apaku@gmx.de">apaku@gmx.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 23.11.10 05:09:05, Aleix Pol wrote:<br>
> Hey :)<br>
> Good news KDevelop'ers! Our official repositories are now in git.kde.orgservers.<br>
<br>
</div>Great, no more downtimes :)<br>
<div class="im"><br>
> This means, you'll find the relevant URL's in<br>
</div>> <a href="https://projects.kde.org/projects/extragear/kdevelop" target="_blank">https://projects.kde.org/projects/extragear/kdevelop</a><<a href="https://projects.kde.org/projects/extragear/kdevelop?jump=repository" target="_blank">https://projects.kde.org/projects/extragear/kdevelop?jump=repository</a>>,<br>
<div class="im">> you can find more information regarding that infrastructure in:<br>
> <a href="http://community.kde.org/Sysadmin/GitKdeOrgManual" target="_blank">http://community.kde.org/Sysadmin/GitKdeOrgManual</a> .<br>
><br>
> I'd like to ask the developers with pending merge requests to move to the<br>
> review board platform so that we can keep working together.<br>
<br>
</div>Hmm. Looking at the manual would it be better to move the MR's to a<br>
scratch pad repository or should people create a personal clone of the<br>
relevant repository? Using a purely local clone for reviewing would be<br>
ok, but IMHO for final merging we shouldn't use the patch file, but<br>
merge the actual branch.<br></blockquote><div>We can relate ReviewBoard to a branch, the good thing about review board it that it eases the reviewing and that's what we should rule for.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
> PS: Now gitorious repository is read-only, how does the kdevelop website<br>
> work? do we have to change the address anywhere? who can do that?<br>
<br>
</div>I believe the wiki has references to the url in the "howto compile"<br>
section. I don't think the website itself has any references on it, its<br>
basically dead since almost a year.<br></blockquote><div>True, we will have to update gitorious references in the wiki and... well, everywhere.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
> PS2: kdevelop-team still has write rights in the gitorious repos just in<br>
> case, that doesn't mean we have to use it :)<br>
<br>
</div>I suggest to turn that off asap to prevent accidents. There's no reason<br>
to keep write access if we can write to the new repo.</blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Andreas<br>
<font color="#888888"><br>
--<br>
Do something unusual today. Pay a bill.<br>
</font><div><div></div><div class="h5"><br>
--<br>
KDevelop-devel mailing list<br>
<a href="mailto:KDevelop-devel@kdevelop.org">KDevelop-devel@kdevelop.org</a><br>
<a href="https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel" target="_blank">https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel</a><br>
</div></div></blockquote></div><br>