All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Viro <aviro@redhat.com>
To: Eric Paris <eparis@redhat.com>
Cc: linux-audit <linux-audit@redhat.com>
Subject: Re: new git tree with audit development
Date: Wed, 9 Jan 2008 08:04:13 -0500	[thread overview]
Message-ID: <20080109130413.GG16537@devserv.devel.redhat.com> (raw)
In-Reply-To: <1199832657.6089.40.camel@localhost.localdomain>

On Tue, Jan 08, 2008 at 05:50:57PM -0500, Eric Paris wrote:
> I've spent the last couple days trying to get all of the latest audit
> development pulled into one place so it can be sent upstream.  Some of
> my patches in this tree haven't been sent to the list and I plan to do
> that tomorrow.  But if anyone sent a patch to the list or has a patch
> for the audit system they want to see in the next kernel release drop me
> a note.  This tree has all of the work I know about.
> 
> http://git.infradead.org/?p=users/eparis/audit.git

Thanks, grabbed.  I'll go over that stuff and push towards -mm by tonight.

      reply	other threads:[~2008-01-09 13:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-08 22:50 new git tree with audit development Eric Paris
2008-01-09 13:04 ` Alexander Viro [this message]

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=20080109130413.GG16537@devserv.devel.redhat.com \
    --to=aviro@redhat.com \
    --cc=eparis@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.