From: Amy Griffis <amy.griffis@hp.com>
To: Robert Giles <rgiles@arlut.utexas.edu>
Cc: linux-audit@redhat.com
Subject: Re: audit-current git
Date: Thu, 8 Jun 2006 18:29:19 -0400 [thread overview]
Message-ID: <20060608222919.GA4667@zk3.dec.com> (raw)
In-Reply-To: <Pine.CYG.4.64.0606081625070.1652@ninja>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 1418 bytes --]
Robert Giles wrote: [Thu Jun 08 2006, 05:30:14PM EDT]
> Howdy folks - this isn't really an audit related question, but where do
> all the [PATCH git] fixes end up after being posted to the list?
I don't know if this is really the correct syntax, but I've been using
[PATCH git] to indicate a fix against a patch in the git tree, versus
[PATCH] for a new patch.
> I'm looking at http://www.kernel.org/git/, and the last change to the
> "audit-current" git tree was four weeks ago (but there have been quite a
> few [PATCH git] postings to the list since then).
Patches usually sit in the latest lspp branch (currently lspp.b18) for
a while before being pulling into the master branch. Additionally,
each time the branch is incremented to a new version, fixes get folded
into their respective patches.
Check out:
http://kernel.org/git/?p=linux/kernel/git/viro/audit-current.git;a=shortlog;h=lspp.b18
for the recent stuff.
> Also - the "audit-current" that's up there now (based on 2.6.17-rc3) works
> great on SuSE 10.1 + audit-1.2.2 with filesystem watches (THANKS!!!).
>
> -----------------------------------------------------------
> Robert Giles Group System Administrator
> SPD/ARL:UT (512) 835-3077 · Fax (512) 490-4244
> --
> Linux-audit mailing list
> Linux-audit@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-audit
prev parent reply other threads:[~2006-06-08 22:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-08 21:30 audit-current git Robert Giles
2006-06-08 22:29 ` Amy Griffis [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=20060608222919.GA4667@zk3.dec.com \
--to=amy.griffis@hp.com \
--cc=linux-audit@redhat.com \
--cc=rgiles@arlut.utexas.edu \
/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