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

List:       kde-i18n-doc
Subject:    Re: Moving Pology into a Git repository
From:       Luigi Toscano <luigi.toscano () tiscali ! it>
Date:       2019-06-15 10:48:08
Message-ID: b8fffdb2-9dbd-8537-00a7-058192984284 () tiscali ! it
[Download RAW message or body]

Nicolás Alvarez ha scritto:
> El mié., 12 de jun. de 2019 a la(s) 19:11, Alexander Potashev
> (aspotashev@gmail.com) escribió:
>>
>> чт, 28 февр. 2019 г. в 01:49, Alexander Potashev <aspotashev@gmail.com>:
>>>
>>> чт, 28 февр. 2019 г. в 01:37, Albert Astals Cid <aacid@kde.org>:
>>>>
>>>> El dimecres, 27 de febrer de 2019, a les 23:29:49 CET, Alexander Potashev va escriure:
>>>>> AFAIK there is a "trunk" branch and tags (
>>>>> https://websvn.kde.org/tags/pology/ ) to migrate. However I have no
>>>>> idea how to pull them both into Git effectively, since KDE SVN has too
>>>>> many commits.
>>>
>>> I also found https://websvn.kde.org/branches/pology/ , may be
>>> Chusslove can tell if there are any other branches.
>>
>> Hi Nicolas,
>>
>> Any news on this migration to Git? Shall I create a KDE Sysadmin
>> ticket on Phabricator?
> 
> I totally forgot about this >_<
> 
> So, I just did in 3 hours what you requested 3 months ago (shame on
> me) and converted pology to git. I pushed it here (cgit/anongit didn't
> pick it up yet, but cloning over ssh will definitely work):
> https://cgit.kde.org/scratch/nalvarez/pology-converted.git
> 
> You can create a sysadmin ticket to ask the repository to be moved to
> its final location.
> 


Should we think about a way for decoupling the language-specific rules which
may not be generic enough to end up in the global repository, and move them to
a separate repository, or is it fine as it is now?

Ciao
-- 
Luigi

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