[Kde-scm-interest] initial port of scripty to git is ready

[Ian Monroe]

On Thu, May 21, 2009 at 8:39 AM, Matt Rogers <mattr at kde.org> wrote:
>
> On May 21, 2009, at 8:16 AM, Ian Monroe wrote:
>
>> On Wed, May 20, 2009 at 10:34 PM, Matt Rogers <mattr at kde.org> wrote:
>>> Hi,
>>>
>>> I've finished an initial port of scripty to git. It can found on
>>> Gitorious at http://gitorious.org/scripty. There are several issues,
>>> if you want to call them that, with it:
>>>
>>> 1. completely untested
>>
>> pinotree says they only way they test is very carefully with the real
>> scripty. This makes me sad. Maybe we could get an anonsvn server
>> cloned and made writable, then we could have something to test with.
>>
>>> 2. there is no initial git clone to get a working copy if it is
>>> missing since I don't know what the layout of the new git
>>> repositories
>>> is going to look like.
>>> 3. There is no 'git push' back into the main repository from
>>> scripty's
>>> clone
>>
>> So that we're on the same page... scripty still needs to work with
>> i18n in SVN. I was a little concerned when you said its a "git port"
>> when its really more of a "git feature addition." I guess I should've
>> dented immediately. :)
>>
>> The idea is that for Amarok or Plasma to switch to git tomorrow, i18n
>> needs to stay in SVN. (Possibly i18n could stay in SVN forever, they
>> have a very different way of doing things and switching to git should
>> be up to them.)
>>
>> The only thing that needs to be git pushed are the .desktop files that
>> scripty famously commits in our SVN repos routinely at the moment.
>>
>> Ian
>
> *sigh* brilliant. too bad nobody told me this initially when i said i
> would do it.
>
> Is there anything else I should know before I keep working on this? Or
> should I give up now and just let it go back to bitrotting?

I totally remember having a conversation with you about it (a long
time ago)! But maybe it was someone else. I explained the plans
several times.

Please don't give up, your the only person with interest that hasn't
recoiled at Perl code. If you want to be sure about things before
continuing you could email this and the i18n list with your
understanding of what the design should be.

Ian