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

List:       kde-core-devel
Subject:    Re: splitting up kdebase in git
From:       Ingo =?utf-8?q?Kl=C3=B6cker?= <kloecker () kde ! org>
Date:       2011-02-12 23:55:58
Message-ID: 201102130056.09614 () thufir ! ingo-kloecker ! de
[Download RAW message or body]


On Saturday 12 February 2011, Tom Albers wrote:
> ----- Original Message -----
> 
> > On Saturday, February 12, 2011 19:12:41 Tom Albers wrote:
> > > ----- Original Message -----
> > > 
> > > > Hi,
> > > > 
> > > > Our default wallpapers used to be part of kdebase/workspace,
> > > > but during
> > > > the git migration they've been removed from workspace due the
> > > > size of
> > > > that directory.
> > > > Wallpapers can't be kept in a git repository because every time
> > > > a git
> > > > repository is cloned all the history (including old wallpapers)
> > > > is cloned. So actually wallpapers are nowhere, should we move
> > > > wallpapers
> > > > back to trunk/KDE/kdebase/workspace?
> > > > 
> > > > Bye,
> > > > Davide Bettio.
> > > 
> > > Maybe just a tarball somewhere? SVN won't stay around, so we need
> > > another
> > > solution i think.
> > 
> > I thought we were keeping SVN around for translations? Or will they
> > simply
> > migrate after the rest of the modules have?
> 
> I personally have no intention to maintain two revision control
> systems.

I understood that SVN would stay indefinitely (read-only) because the 
Git repos do not carry the full history. (Of course a read-only SVN 
won't really help with the wallpapers.)


Regards,
Ingo

["signature.asc" (application/pgp-signature)]

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