Ian Monroe wrote:
> 2009/6/11 Jeff Mitchell :
>> Thomas Zander wrote:
>>> On Thursday 11. June 2009 21.27.11 Chani wrote:
so now... what's the next step? who's going to work on hooking up things
like the commit filter and bko and other commit-hooks so that amarok
keeps those when it
Thomas Zander wrote:
>If we agree that using gitorious.org is a good thing (I think we had
>consensus there) that means that most of that will be done on the
> server. They already have css feeds for each project and module etc so
> you can listen to those.
That is not the consensus. Our sysadmins
2009/6/11 Jeff Mitchell :
> Thomas Zander wrote:
>> On Thursday 11. June 2009 21.27.11 Chani wrote:
>>> so now... what's the next step? who's going to work on hooking up things
>>> like the commit filter and bko and other commit-hooks so that amarok
>>> keeps those when it moves into git? :) I can'
Thomas Zander wrote:
> On Thursday 11. June 2009 21.27.11 Chani wrote:
>> so now... what's the next step? who's going to work on hooking up things
>> like the commit filter and bko and other commit-hooks so that amarok
>> keeps those when it moves into git? :) I can't remember if anyone's done
>> a
On Thursday 11. June 2009 21.27.11 Chani wrote:
> so now... what's the next step? who's going to work on hooking up things
> like the commit filter and bko and other commit-hooks so that amarok
> keeps those when it moves into git? :) I can't remember if anyone's done
> any of that yet.
If we agre
so scripty pushed .desktop files to git-test without issues :)
there are still some improvements I want to make (like being able to skip a
failed module instead of aborting the whole thing) but it is essentially
working.
so now... what's the next step? who's going to work on hooking up things li