Linux-audit Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Viro <aviro@redhat.com>
To: linux-audit@redhat.com
Cc: akpm@osdl.org
Subject: git tree updates
Date: Mon, 22 May 2006 02:25:55 -0400	[thread overview]
Message-ID: <20060522062555.GG23180@devserv.devel.redhat.com> (raw)

* new branches: audit.b15, master.b15, lspp.b15; tree pushed to git.kernel.org
* changes:
	moved everything except Amy's patches to master.b15
	added: belated removal of audit_panic() stub from include/linux/audit.h
	fixes present in lspp.b14 folded into corresponding patches
	fixed and folded:
		+ reordering breakage spotted by akpm (audit_cmd_mutex used
		  before renaming audit_netlink_mutex -> audit_cmd_mutex).
		+ Linda's IPC patch forgot to update stub of
		  audit_ipc_set_perm()
	Amy's patches are in lspp.b15, ported to current mainline tree (the
	first one needed some work on conflict resolution).

master.b15 is -mm fodder; it does obsolete git-audit-master-build-fix.patch
and audit-build-fix.patch currently in -mm.

Steve, patches for lspp kernel had been updated, pick them in usual place.

                 reply	other threads:[~2006-05-22  6:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20060522062555.GG23180@devserv.devel.redhat.com \
    --to=aviro@redhat.com \
    --cc=akpm@osdl.org \
    --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