[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-release-team
Subject:    Re: [Kde-scm-interest] Re: Kate App/Part/KWrite => kate.git
From:       Tom Albers <toma () kde ! org>
Date:       2011-01-29 12:36:07
Message-ID: 1746008737.171783.1296304567772.JavaMail.root () contact ! kovoks ! nl
[Download RAW message or body]



----- Original Message -----
> A Dissabte, 29 de gener de 2011, Christoph Cullmann va escriure:
> > On Sunday 16 January 2011 13:11:47 Christoph Cullmann wrote:
> > > Hi,
> > >
> > > is it ok to now move that stuff to the kate.git for KDE 4.7?
> > > KTextEditor can reside in kdelibs, to keep BC /SC (I will sync it
> > > if
> > > changes occur).
> > >
> > > This would remove:
> > >
> > > kdelibs/kate
> > > kdesdk/kate
> > > kdebase/apps/kwrite
> > >
> > > (and I guess the doc/.. stuff for the apps need to move and
> > > what-I-don't
> > > know i18n scripts + packaging must change)
> > >
> > > But the part/application code really should be only in one place.
> > > Given that most people work only in kate.git, this will avoid my
> > > hassle
> > > with syncs, I will only keep syncing /trunk => git, to avoid any
> > > losses
> > > until this is done, thought.
> >
> > As no reaction until now and kdelibs moves git now already, I intend
> > to
> > move kate part out of kdelibs and only let it be in kate.git (same
> > for
> > kwrite in kdebase and kate in kdesdk).
> >
> > I propose the weekend 15.-16. Feb for the move (which more or less
> > would
> > only be a delete in git/svn of the old copies).
> >
> > I guess this needs coordination to have for example still working
> > i18n (as
> > the docbooks would move too and the i18n stuff needs fixing).
> > Therefore CC Albert, would that date be ok for you to help me a bit
> > with
> > this? Or should I delay and ask on i18n for help?
> >
> > With kdelibs now being a git, it really is not that nice for
> > contributors
> > of kate part to clone whole kdelibs...
> 
> I'm sorry but having an own repo for kate with all the stuff in there
> is a no
> go from the i18n point of view.
> 

Because the tool can not cope with it?
-- 
Tom Albers
KDE Sysadmin
_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team
[prev in list] [next in list] [prev in thread] [next in thread]