On 21. 10. 2011 Myriam Schweingruber wrote: > Hi Matej, Hi Myriam and list!
> I have seen you are working on iPod problems in Amarok. That is really > great, as we need help in this :) Welcome on board! Glad to work with such a wonderful team. :) Hello all Amarok devs. > I would like to invite you to the #amarok.dev channel on > irc.freenode.net. It is a more quiet channel for the Amarok team where > we can discuss more easily. > Also please do subscribe to amarok-devel@kde.org where all important > information is found. Already subscribed to the list, but I didn't know about the channel, thanks. (I even searched for something similar with no luck) > Just a side note: you should not reassign bugs to you, because that > makes then disappear from the mailinglist we use for bugtracking. You > can subscript to the bugs, that should be enough for your personal > tracking. Ah, sorry about that, I should have asked first. A.d. personal tracking - do you mean adding myself to the CC list? I wanted to differentiate somehow between bugs I work on and these where I am part of the "reporting" side. One last question, what is the preferred way of letting my patches be reviewed once I have developer access? I have 5 small and unrelated iPod patches in my git repo - should I: a) create my amarok git clone on git.kde.org and push there (perhaps to a branch) b) create a branch (ipod-fixes) on git.kde.org:amarok.git and push there c) send them to amarok-dev using `git format-patch` (the Linux kernel way) d) upload them one-by-one to reviewboard (this one seems little inconvenient) I miss something like pull requests from github where a series of patches can be reviewed without squelching them into one. Regards, Matěj Laitl (aka strohel on IRC) _______________________________________________ Amarok-devel mailing list Amarok-devel@kde.org https://mail.kde.org/mailman/listinfo/amarok-devel