On 17-08-2015 10:28, Ruben Undheim wrote:
Are there any others that may cause data-loss for users, that are
fixed in sid and have patches available like #787419 and #748469?
There is also #788002
> We might first try backporting fixes for 3 of them, then backpedal on
> #771205 if it is met with resistance again.
I think we should concentrate on bugs that are so serious that they cause
data-loss
for users (crash). That is beneficial for everyone, and also the Stable Release
team would
be
I do obviously think that this bug qualify for that. Apparently #771205 was
considered
not release-critical in the freeze time, so we should not include that one then.
#748469 is probably a candidate since it sounds quite annoying although I
haven't
experienced it myself.
We might first try ba
> This actually is not the only annoying bug that is fixed in an upstream
> point release (see #748469 and #771205 for the others).
>
> As I understand, maintainers are open up to the idea of backporting fixes to
> gtk+3.0 in jessie, but they don't want to deal with stable release team for
> accep
On Mon, 3 Aug 2015 13:34:03 +0200 Ruben Undheim
wrote:
>
> Can you please target this bug fix for jessie so that I can recommend
> jessie to people without having to add: "but you need to make sure to
> manually patch libgtk-3 unless you want a painful experience"?
>
Hi, Ruben
This actually i
Hi,
I assume that none of the maintainers of gtk+3.0 actually work with
multiple terminal windows of gnome-terminal opened up at
the same time? Because if they/you do, I assume that they would
realise how annoying it is when suddenly out of nowhere all of them
just freeze and you loose the "work"
6 matches
Mail list logo
