From: Richard Guy Briggs <rgb@redhat.com>
To: William Roberts <bill.c.roberts@gmail.com>
Cc: linux-audit@redhat.com
Subject: Re: [PATCH] audit: Add cmdline to taskinfo output
Date: Mon, 28 Oct 2013 17:52:24 -0400 [thread overview]
Message-ID: <20131028215224.GA16042@madcap2.tricolour.ca> (raw)
In-Reply-To: <CAFftDdrcu=g7PxZJ-RCfprT+EyssxDDyBCeWTZjjy_+YzOmByA@mail.gmail.com>
On Mon, Oct 28, 2013 at 12:02:42PM -0700, William Roberts wrote:
> On Mon, Oct 28, 2013 at 9:30 AM, William Roberts
> <bill.c.roberts@gmail.com>wrote:
> > On Mon, Oct 28, 2013 at 8:10 AM, Richard Guy Briggs <rgb@redhat.com>wrote:
> >> On Mon, Oct 28, 2013 at 06:48:48AM -0700, William Roberts wrote:
> >> > On Wed, Oct 23, 2013 at 1:40 PM, William Roberts <bill.c.roberts@gmail.com>wrote:
> >> > A few notes on this moving forward:
> >> > 4. This could be a dynamic on/off setting, which brings me to my
> >> > question, of: "What is the status of E.Paris's generic feature
> >> > set/get" patches fare? This is a great use case for those.
> >>
> >> I've queued his patchset for linux-next to be pushed just after v3.12
> >> release.
>
> By any chance do you have a public tree I can configure you as a remote?
It is currently here,
git://toccata2.tricolour.ca/linux-2.6-rgb.git
with branches
audit-for-next
audit-for-linus
but in the future, an updated link should be findable here if it moves:
http://people.redhat.com/rbriggs/
> >> - RGB
> >
> > William C Roberts
>
> William C Roberts
- RGB
--
Richard Guy Briggs <rbriggs@redhat.com>
Senior Software Engineer
Kernel Security
AMER ENG Base Operating Systems
Remote, Ottawa, Canada
Voice: +1.647.777.2635
Internal: (81) 32635
Alt: +1.613.693.0684x3545
next prev parent reply other threads:[~2013-10-28 21:52 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 20:40 [PATCH] audit: Add cmdline to taskinfo output William Roberts
2013-10-24 19:10 ` Richard Guy Briggs
2013-10-28 13:48 ` William Roberts
2013-10-28 15:10 ` Richard Guy Briggs
2013-10-28 16:30 ` William Roberts
2013-10-28 19:02 ` William Roberts
2013-10-28 21:52 ` Richard Guy Briggs [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-10-28 23:47 William Roberts
2013-10-28 23:50 William Roberts
2013-10-29 15:14 ` Steve Grubb
2013-10-29 17:44 ` William Roberts
2013-10-29 17:55 ` William Roberts
2013-10-29 19:01 ` Steve Grubb
2013-10-29 19:12 ` William Roberts
2013-10-29 19:55 ` Steve Grubb
2013-10-29 20:25 ` William Roberts
2013-10-29 23:24 ` William Roberts
2013-10-30 0:43 ` William Roberts
2013-10-30 19:42 ` Steve Grubb
2013-10-30 20:18 ` William Roberts
2013-10-30 21:20 ` Eric Paris
2013-10-30 21:52 ` William Roberts
2013-10-31 14:36 ` Steve Grubb
2013-10-31 15:24 ` William Roberts
2013-10-31 15:28 ` Richard Guy Briggs
2013-10-31 15:33 ` William Roberts
2013-10-31 15:46 ` Richard Guy Briggs
2013-10-31 15:51 ` William Roberts
2013-10-31 15:52 ` William Roberts
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=20131028215224.GA16042@madcap2.tricolour.ca \
--to=rgb@redhat.com \
--cc=bill.c.roberts@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