From: Laszlo Ersek <lersek@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>,
Cole Robinson <crobinso@redhat.com>,
qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] [trivial PATCH 2.0 0/1] silence invalid cyrus-sasl warning on startup
Date: Fri, 14 Mar 2014 15:39:35 +0100 [thread overview]
Message-ID: <1394807976-9469-1-git-send-email-lersek@redhat.com> (raw)
Here's a patch that suits my mental capabilities on this
Friday afternoon.
Laszlo Ersek (1):
sasl: Avoid 'Could not find keytab file' in syslog
qemu.sasl | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
--
1.8.3.1
next reply other threads:[~2014-03-14 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 14:39 Laszlo Ersek [this message]
2014-03-14 14:39 ` [Qemu-devel] [trivial PATCH 2.0 1/1] sasl: Avoid 'Could not find keytab file' in syslog Laszlo Ersek
2014-03-14 14:42 ` Cole Robinson
2014-03-14 15:43 ` [Qemu-devel] [Qemu-trivial] " Michael Tokarev
2014-03-14 15:46 ` Cole Robinson
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=1394807976-9469-1-git-send-email-lersek@redhat.com \
--to=lersek@redhat.com \
--cc=crobinso@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).