From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: Alexander <goal81@gmail.com>
Subject: Re: Regarding bug 435682
Date: Sat, 3 Dec 2011 08:44:50 -0500 [thread overview]
Message-ID: <201112030844.51025.sgrubb@redhat.com> (raw)
In-Reply-To: <CACMUsGwPbWN=teC4yeqyq6+qSRMcmyTLkBBe38rkCuEmKYLp=w@mail.gmail.com>
On Friday, October 28, 2011 09:56:48 AM Alexander wrote:
> Here's another version of the patch for version 2.1.3 which solves bug
> 435682 (https://bugzilla.redhat.com/show_bug.cgi?id=435682).
> Seems to be slightly better than previous version, 'cause now it's using
> something like escape sequence to handle filenames with spaces.
Applied a slightly modified version of the patch:
https://fedorahosted.org/audit/changeset/608
Thanks,
-Steve
next prev parent reply other threads:[~2011-12-03 13:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 13:56 Regarding bug 435682 Alexander
2011-12-03 13:44 ` Steve Grubb [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-10-20 14:48 Alexander
2011-10-21 12:49 ` Miloslav Trmac
2011-10-21 12:58 ` Steve Grubb
2011-10-21 13:03 ` Alexander
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=201112030844.51025.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=goal81@gmail.com \
--cc=linux-audit@redhat.com \
/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