qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Alberto Garcia <berto@igalia.com>
Cc: qemu-devel@nongnu.org, Cole Robinson <crobinso@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] gtk: don't leak the GtkBorder with VTE 0.36
Date: Fri, 13 May 2016 14:29:06 +0200	[thread overview]
Message-ID: <1463142546.14138.67.camel@redhat.com> (raw)
In-Reply-To: <1463127654-5171-1-git-send-email-berto@igalia.com>

On Fr, 2016-05-13 at 11:20 +0300, Alberto Garcia wrote:
> When gtk_widget_style_get() is used to get the "inner-border" style
> property, it returns a copy of the GtkBorder which must be freed by
> the caller.
> 
> This patch also fixes a warning about the unused 'padding' structure
> with VTE 0.36.

Thanks, added.  Had to adjust it a bit b/c I fixed the warning in cole's
patch already so the patch didn't apply cleanly any more.

cheers,
  Gerd

           reply	other threads:[~2016-05-13 12:29 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1463127654-5171-1-git-send-email-berto@igalia.com>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1463142546.14138.67.camel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=berto@igalia.com \
    --cc=crobinso@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).