<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im"><br>
> You're free to have your own, differing opinion; just be aware that I for<br>
one don't share it.<br>
</div>That's just fair and the good reason for at least some options ;-)<br>
(Even the Bespin hack allowed you to turn off the animation)<br>
<div class="im"><br>
> between 2% and 5%, which is OK, but I've seen 20% or even more on<br>
> other days. Anyway, since it's mostly a background app, I want it to<br>
> be lightweight.<br>
</div>Temporarily? Database updates?<br>
<div class="im"><br>
> Go ahead then, submit a patch :-)<br>
</div>With pleasure, but might i kindly ask again for git push access (of reviwed<br>
patches of course) because patching, sending patches by mail and then running<br>
into a conflict with your own patch frankly sucks. :-(<br>
(Maybe I'm just failing git, though - advice is appreciated)</blockquote><div><br></div><div>I don't really feel like getting involved technically in this discussion. But regarding git workflow:</div><div><br></div>
<div> The easiest thing for both you and us is for you to work in a branch (or more branches) in your clone of amarok's repo. Then you can keep up to date by merging/rebasing from the main Amarok repo, while still working away in your place. You can then submit a merge request automatically (there is a button in the gitorious interface) which automatically emails us and allows us to check out the branch and merge it.</div>
<div><br></div><div>See this for more info:</div><div><br></div><div><a href="http://techbase.kde.org/Getting_Started/Sources/Amarok_Git_Tutorial#Patch_Contributors">http://techbase.kde.org/Getting_Started/Sources/Amarok_Git_Tutorial#Patch_Contributors</a></div>
<div><br></div><div>leo </div></div><br clear="all"><br>-- <br>______________________________________________________<br><a href="mailto:lfranchi@kde.org">lfranchi@kde.org</a> Tufts University 2010<br>
<a href="mailto:leonardo.franchi@tufts.edu">leonardo.franchi@tufts.edu</a> The KDE Project<br>