qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: av1474@comtv.ru, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] audio: Drop superfluous conditionals around g_free()
Date: Tue, 10 Jun 2014 10:00:34 +0200	[thread overview]
Message-ID: <1402387234.8739.20.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <87lhtadljv.fsf@blackfin.pond.sub.org>

  Hi,

> Gerd, should patches for audio/ conform to the usual style now, or are
> they still special?

I don't consider them special.  If you use usual qemu style in patches
that is fine with me.  But I don't feel like doing a conversion pass,
that simply isn't worth the trouble IMO.

cheers,
  Gerd

  reply	other threads:[~2014-06-10  8:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-06 16:35 [Qemu-devel] [PATCH] audio: Drop superfluous conditionals around g_free() Markus Armbruster
2014-06-06 16:43 ` Eric Blake
2014-06-06 16:56   ` Markus Armbruster
2014-06-10  8:00     ` Gerd Hoffmann [this message]
2014-06-12 11:42 ` Gerd Hoffmann

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=1402387234.8739.20.camel@nilsson.home.kraxel.org \
    --to=kraxel@redhat.com \
    --cc=armbru@redhat.com \
    --cc=av1474@comtv.ru \
    --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).