Re: Question about git repository layout + releases

2010-10-28 Thread Christoph Cullmann
On Thursday 21 October 2010 19:48:28 Eike Hein wrote: > On 10/21/2010 07:08 PM, Dominik Haumann wrote: > > This is not entirely correct: True, we want to move the git repo to KDE's > > git infrastructure. Christoph could still merge all changes back to svn > > (just like he does now); this is no is

Re: Question about git repository layout + releases

2010-10-28 Thread Dominik Haumann
On Thursday, 21. October 2010, Eike Hein wrote: > On 10/21/2010 07:08 PM, Dominik Haumann wrote: > > This is not entirely correct: True, we want to move the git repo to > > KDE's git infrastructure. Christoph could still merge all changes back > > to svn (just like he does now); this is no issue. H

Re: Question about git repository layout + releases

2010-10-27 Thread Dominik Haumann
On Thursday, 21. October 2010, David Faure wrote: > On Friday 15 October 2010, Christoph Cullmann wrote: > > On 10/09/2010 02:37 PM, Christoph Cullmann wrote: > > > Hi, > > > > > > Kate is atm in kdesdk, KWrite in kdebase/apps and the part in > > > kdelibs. > > > > > > We played with unifying all

Re: Question about git repository layout + releases

2010-10-22 Thread Dominik Haumann
On Thursday, 21. October 2010, Eike Hein wrote: > On 10/21/2010 07:08 PM, Dominik Haumann wrote: > > This is not entirely correct: True, we want to move the git repo to > > KDE's git infrastructure. Christoph could still merge all changes back > > to svn (just like he does now); this is no issue. H

Re: Question about git repository layout + releases

2010-10-22 Thread Tom Albers
- Oorspronkelijk bericht - > This is not entirely correct: True, we want to move the git repo to > KDE's > git infrastructure. Christoph could still merge all changes back to > svn > (just like he does now); this is no issue. Hence, no problem for the > release > cycle. As Eike said, this

Re: Question about git repository layout + releases

2010-10-21 Thread Eike Hein
On 10/21/2010 07:08 PM, Dominik Haumann wrote: > This is not entirely correct: True, we want to move the git repo to KDE's > git infrastructure. Christoph could still merge all changes back to svn > (just like he does now); this is no issue. Hence, no problem for the release > cycle. Well, that's

Re: Question about git repository layout + releases

2010-10-21 Thread Dominik Haumann
On Thursday, 21. October 2010, Eike Hein wrote: > On 10/21/2010 06:06 PM, David Faure wrote: > > I'm not sure, but it seems to me that the sysadmin team (not me, the > > actual sysadmins) has currently a better overview on the git migration > > than release- team. You should probably ask them (#kde

Re: Question about git repository layout + releases

2010-10-21 Thread Eike Hein
On 10/21/2010 06:06 PM, David Faure wrote: > I'm not sure, but it seems to me that the sysadmin team (not me, the actual > sysadmins) has currently a better overview on the git migration than release- > team. You should probably ask them (#kde-sysadmin on irc, or sysadmin@ email). Actually we (sys

Re: Question about git repository layout + releases

2010-10-21 Thread David Faure
On Friday 15 October 2010, Christoph Cullmann wrote: > On 10/09/2010 02:37 PM, Christoph Cullmann wrote: > > Hi, > > > > Kate is atm in kdesdk, KWrite in kdebase/apps and the part in kdelibs. > > > > We played with unifying all three parts (+ the ktexteditor interfaces) in > > one git repository

Re: Question about git repository layout + releases

2010-10-17 Thread Christoph Cullmann
On 10/09/2010 02:37 PM, Christoph Cullmann wrote: > Hi, > > Kate is atm in kdesdk, KWrite in kdebase/apps and the part in kdelibs. > > We played with unifying all three parts (+ the ktexteditor interfaces) in one > git repository on gitorious since some months. > > It makes development much easier,

Question about git repository layout + releases

2010-10-09 Thread Christoph Cullmann
Hi, Kate is atm in kdesdk, KWrite in kdebase/apps and the part in kdelibs. We played with unifying all three parts (+ the ktexteditor interfaces) in one git repository on gitorious since some months. It makes development much easier, given most times you need to touch all parts (beside the int