On Mon, 2014-04-28 at 08:45 +0200, Daniel Pocock wrote:
> Even if there are no other fixes you plan to backport, could you
> consider making a 3.4.5 tag just with this fix?
Hi,
right, I understand the Long Term Support "models" and so on, but it's a
distribution decision. I'm not a fan of tweaking upstream "effectively
dead" code with random patches proposed by individuals, especially for
such old branch. There are always exceptions, but anyway. The
distributions have always a choice to patch the sources on their own,
which they do. I also understand your idea of sharing the change with
others, which is good, though I would be able to find another 10+ fixes
which would be good to have in 3.4.4, but which landed between it and
the current 3.12.1 stable release. And that's the reason why I do not
like to patch the dead code.
> It is not quite so easy though - the URL handling is usually not hard,
> the question is how do we route the event to the right phone. I'll put
> more details in a separate bug.
Please do, we can find some solution for it, I hope. (I thought your URL
handler, system-registered, will do all necessary, like when user clicks
an http:// URL, which will open his/her set web browser.)
Bye,
Milan
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
