<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, May 31, 2013 at 10:43 AM, Albert Astals Cid <span dir="ltr"><<a href="mailto:aacid@kde.org" target="_blank">aacid@kde.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">El Divendres, 31 de maig de 2013, a les 17:37:22, Urs Wolfer va escriure:<br>
<div class="im">> Ok, let's check what's the current status:<br>
><br>
> filesharing, krdc, and now also kdenetwork-strigi-analyzers are<br>
> maintainer approved.<br>
><br>
> kdnssd and kppp have been shorty checked by me and they look ok (though<br>
> it would be a good idea if somebody else could check also).<br>
><br>
> kopete: @Pali, is it ready?<br>
><br>
> the krfb maintainer has not answered yet; probably we should check that<br>
> repo as well.<br>
><br>
> @Jeremy: Anything that needs to be done before the final conversion?<br>
<br>
</div>Coordinate with the release team so you don't do the move close to any release<br>
date and with the i18n team so we update the scripty files.<br>
<br></blockquote><div><br></div><div style>Yep, looking at the kde calendar, 4.10.4 is to be released next tuesday (June 4th) and then 4.11 beta 1 will be tagged on June 12th, so we ought to try to shoot for that window, preferably as early as possible in that window so any issues can get fixed before 4.11 beta 1 tagging.</div>
<div style><br></div><div style>Urs, did you file the bugs for the git repos yet? or shall I do that?</div><div style><br></div><div style>thanks,</div><div style>Jeremy</div><div style> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Cheers,<br>
Albert<br>
<div class="HOEnZb"><div class="h5"><br>
><br>
> Bye<br>
> urs<br>
><br>
> On 2013-05-24 21:58, Jeremy Whiting wrote:<br>
> > Hi Urs,<br>
> ><br>
> > On Fri, May 24, 2013 at 10:38 AM, Urs Wolfer <<a href="mailto:uwolfer@kde.org">uwolfer@kde.org</a>> wrote:<br>
> >> Hi Jeremy<br>
> >><br>
> >> Now it looks like tags got lost?<br>
> ><br>
> > Nope, I just forgot to push them, pushing them now.<br>
> ><br>
> ><br>
> >> CMakeList.txt history looks good IMHO now.<br>
> >><br>
> >> Also, I think you can drop the branch "make_kget_cool" if you do<br>
> >> not have any reason for keeping it. Do you think there is no need<br>
> >> for an "orignal" branch because the "make_kget_cool" branch is based<br>
> >> (?) on this branch?<br>
> ><br>
> > Ok, we can easily delete that branch afterwards, we could make the<br>
> > "master" branch before rev 478995 on an "original" branch. I'll look<br>
> > into that. I think the existing make_kget_cool branch that's also<br>
> > master works ok and we can just nuke make_kget_cool before pushing<br>
> > since it's very old.<br>
> ><br>
> > BR<br>
> > Jeremy<br>
> ><br>
> ><br>
> >> Bye<br>
> >> urs<br>
> >><br>
> >> On 2013-05-23 18:46, Jeremy Whiting wrote:<br>
> >>> ok, fixed the rules a bit by adding the work branch<br>
> >>> make_kget_cool and<br>
> >>> pushed to scratch/whiting/kget. It looks good except for an old<br>
> >>> master branch of doc stuff that didn't get merged in somehow<br>
> >>> (something wrong with the rules only I'm<br>
> ><br>
> > sure). <a href="http://quickgit.kde.org/?p=scratch%2Fwhiting%2Fkget.git&a=history&h" target="_blank">http://quickgit.kde.org/?p=scratch%2Fwhiting%2Fkget.git&a=history&h</a><br>
> > =dd40536f1643209d157cba75adc70fe36712e05f&f=CMakeLists.txt><br>
> >>> [1]<br>
> >>> [3] looks like it includes all history for CMakeLists.txt now.<br>
> >>> I'll<br>
> >>><br>
> >>> look at the master branch with doc stuff in a bit and then we<br>
> >>> should<br>
> >>> be good to go I believe.<br>
> >>><br>
> >>> BR<br>
> >>> Jeremy<br>
> >>><br>
> >>> On Wed, May 22, 2013 at 9:05 AM, Jeremy Whiting<br>
> >>> <<a href="mailto:jpwhiting@kde.org">jpwhiting@kde.org</a>> wrote:<br>
> >>><br>
> >>> Urs,<br>
> >>><br>
> >>> Hmm, looking at the kget git repo I have here I do have<br>
> >>> make_kget_cool branch, but it only goes to rev 407833, also I have<br>
> >>> a master branch that ends at one point. I'll see what I can do<br>
> >>> to clean this up and let you know.<br>
> >>><br>
> >>> BR,<br>
> >>> Jeremy<br>
> >>><br>
> >>> On Wed, May 22, 2013 at 12:44 AM, Urs Wolfer <<a href="mailto:uwolfer@kde.org">uwolfer@kde.org</a>><br>
> >>> wrote:<br>
> >>> Hi Jeremy<br>
> >>><br>
> >>> Lukas Appelhans has noticed an issue in KGet:<br>
> ><br>
> >>> "I'm missing a bit history here. Compare these two:<br>
> > <a href="http://quickgit.kde.org/?p=scratch%2Fwhiting%2Fkget.git&a=history&h=be2aa1" target="_blank">http://quickgit.kde.org/?p=scratch%2Fwhiting%2Fkget.git&a=history&h=be2aa1</a><br>
> > 7d34ebc12e82a5d9275ed0f597ee41929f&f=CMakeLists.txt&pg=1><br>
> >>> [2] [1]<br>
> >>> and<br>
> ><br>
> > <a href="http://websvn.kde.org/trunk/KDE/kdenetwork/kget/CMakeLists.txt?view=log" target="_blank">http://websvn.kde.org/trunk/KDE/kdenetwork/kget/CMakeLists.txt?view=log</a><br>
> ><br>
> >>> [3] [2]<br>
> >>><br>
> >>> The branched commits show fine in websvn (make_kget_cool, at the<br>
> >>> end), while in git, your merge commit is the first one. Is that<br>
> >>> expected behavior?"<br>
> >>><br>
> >>> Jeremy, I think you could do it like KRDC: make a branch<br>
> >>> "original" with all the old commits, and put all commits from the<br>
> >>> "make_kget_cool" branch into master. Also you can drop the Git<br>
> >>> branch "make_kget_cool".<br>
> >>><br>
> >>> Bye<br>
> >>> urs<br>
> >>><br>
> >>> On 2013-05-17 18:19, Jeremy Whiting wrote:<br>
> >>> On Fri, May 17, 2013 at 9:22 AM, Urs Wolfer <<a href="mailto:uwolfer@kde.org">uwolfer@kde.org</a>><br>
> >>> wrote:<br>
> >>><br>
> >>> Ok, I have mailed all maintainers. Once we get their approval, we<br>
> >>> can start the final migration :)<br>
> >>><br>
> >>> Should I request Git repos for every project from KDE sysadmins?<br>
> >>><br>
> >>> Yes, you can, make sure you ask to add me (whiting) as a Project<br>
> >>> Manager so I can push the conversions.<br>
> >>><br>
> >>> Pali, I'm using the modified svn-all-fast-export to match files,<br>
> >>> does<br>
> >>> my kopete git repo on scratch/whiting/kopete differ from yours?<br>
> >>> If<br>
> >>> not it'd probably be simplest for me to just push all the<br>
> >>> conversions<br>
> >>> from here when we do the final one.<br>
> >>><br>
> >>> BR,<br>
> >>> Jeremy<br>
> >>><br>
> >>><br>
> >>> @Pali: What do you think about Kopete? Is it also ready?<br>
> >>><br>
> >>> Bye<br>
> >>> urs<br>
> >>><br>
> >>> On 2013-05-17 17:01, Jeremy Whiting wrote:<br>
> >>><br>
> >>> On Thu, May 16, 2013 at 11:48 PM, Urs Wolfer <<a href="mailto:uwolfer@kde.org">uwolfer@kde.org</a>><br>
> >>> wrote:<br>
> >>><br>
> >>> Hi Jeremy<br>
> >>><br>
> >>> I have had a look at KRDC and it looks really good. I have found<br>
> >>> no issues so far.<br>
> >>><br>
> >>> So, what's next? Do you think the scripts are almost ready? If<br>
> >>> yes, I think I will notify all maintainers again to check their<br>
> >>> converted repos.<br>
> >>><br>
> >>> Yes, I think it's in very good shape. If you could get<br>
> >>> maintainers to<br>
> >>> check their repos that would be great. And update the table in<br>
> >>> the<br>
> >>> wiki page accordingly.<br>
> >>><br>
> >>> BR,<br>
> >>> Jeremy<br>
> >>><br>
> >>> Links:<br>
> >>> ------<br>
> >>> [1]<br>
> ><br>
> > <a href="http://quickgit.kde.org/?p=scratch%2Fwhiting%2Fkget.git&a=history&" target="_blank">http://quickgit.kde.org/?p=scratch%2Fwhiting%2Fkget.git&a=history&</a>;<br>
> > h=be2aa17d34ebc12e82a5d9275ed0f597ee41929f&f=CMakeLists.txt&pg=1><br>
> >>> [2]<br>
> >>> [2]<br>
> ><br>
> > <a href="http://websvn.kde.org/trunk/KDE/kdenetwork/kget/CMakeLists.txt?view=log" target="_blank">http://websvn.kde.org/trunk/KDE/kdenetwork/kget/CMakeLists.txt?view=log</a><br>
> ><br>
> >>> [3]<br>
> >>> [3]<br>
> ><br>
> > <a href="http://quickgit.kde.org/?p=scratch%2Fwhiting%2Fkget.git&a=history&" target="_blank">http://quickgit.kde.org/?p=scratch%2Fwhiting%2Fkget.git&a=history&</a>;<br>
> > h=dd40536f1643209d157cba75adc70fe36712e05f&f=CMakeLists.txt><br>
> >>> [1]<br>
> ><br>
> > Links:<br>
> > ------<br>
> > [1]<br>
> > <a href="http://quickgit.kde.org/?p=scratch%2Fwhiting%2Fkget.git&a=history&" target="_blank">http://quickgit.kde.org/?p=scratch%2Fwhiting%2Fkget.git&a=history&</a>;<br>
> > h=dd40536f1643209d157cba75adc70fe36712e05f&f=CMakeLists.txt [2]<br>
> > <a href="http://quickgit.kde.org/?p=scratch%2Fwhiting%2Fkget.git&a=history&" target="_blank">http://quickgit.kde.org/?p=scratch%2Fwhiting%2Fkget.git&a=history&</a>;<br>
> > h=be2aa17d34ebc12e82a5d9275ed0f597ee41929f&f=CMakeLists.txt&pg=1<br>
> > [3]<br>
> > <a href="http://websvn.kde.org/trunk/KDE/kdenetwork/kget/CMakeLists.txt?view=log" target="_blank">http://websvn.kde.org/trunk/KDE/kdenetwork/kget/CMakeLists.txt?view=log</a><br>
><br>
</div></div><div class="HOEnZb"><div class="h5">> _______________________________________________<br>
> Kde-scm-interest mailing list<br>
> <a href="mailto:Kde-scm-interest@kde.org">Kde-scm-interest@kde.org</a><br>
> <a href="https://mail.kde.org/mailman/listinfo/kde-scm-interest" target="_blank">https://mail.kde.org/mailman/listinfo/kde-scm-interest</a><br>
</div></div></blockquote></div><br></div></div>