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

List:       kde-i18n-doc
Subject:    Re: Smb4K moved to KDE Review
From:       Burkhard =?ISO-8859-1?Q?L=FCck?= <lueck () hube-lueck ! de>
Date:       2014-01-15 20:08:46
Message-ID: 1514885.zcqtgeKiTY () parodia
[Download RAW message or body]

Am Mittwoch, 15. Januar 2014, 19:23:07 schrieb Albert Astals Cid:
> El Dimecres, 15 de gener de 2014, a les 16:16:38, Burkhard Lück va escriure:
> > Am Dienstag, 14. Januar 2014, 20:47:42 schrieb Alexander Reinholdt:
> > > Hello!
> > > 
> > > I wanted to inform you that Smb4K moved out of playground/network
> > > (Subversion repository) to KDE Review (Git repository).
> > 
> > Thanks
> > 
> > > Smb4K already has got a manual that currently resides in
> > > playground/network/docs. My question is how to deals with it now. Do I
> > > have
> > > to open a sysadmin ticket to let it be moved to the Git repository or is
> > > this triggered/done by you guys?
> > 
> > Afaik the manual in svn was imported as a development snapshot without
> > history some time ago and all changes in playground were done by you
> > (except the "Usual Suspects" fixing minor stuff), so caring about history
> > does not make much sense.
> > 
> > Therefore from my pov you should simply copy the doc dir from svn (and
> > then
> > rm it there) to your smb4k clone from kdereview and commit it.
> 
> +1 Having the doc and the code in different repos does not make any sense.
> 
Yes, digikam + kipi-plugins have this setup (extra repo for docs) and from a 
documentation + doc translation pov that is really a big big mess, see

https://bugs.kde.org/show_bug.cgi?id=329637

Maybe translators should add some comments to this BR.
 
-- 
Burkhard Lück

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