From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Jones Subject: source code control for audit userspace tools Date: Wed, 14 Feb 2007 16:06:08 -0800 Message-ID: <20070215000608.GA17782@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mx1.redhat.com (mx1.redhat.com [172.16.48.31]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l1F0IK4l010084 for ; Wed, 14 Feb 2007 19:18:20 -0500 Received: from mx1.suse.de (ns1.suse.de [195.135.220.2]) by mx1.redhat.com (8.13.1/8.13.1) with ESMTP id l1F0IGO0009725 for ; Wed, 14 Feb 2007 19:18:17 -0500 Received: from Relay2.suse.de (mail2.suse.de [195.135.221.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.suse.de (Postfix) with ESMTP id 3CEBE1251A for ; Thu, 15 Feb 2007 01:07:06 +0100 (CET) Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: linux-audit@redhat.com List-Id: linux-audit@redhat.com I brought this up on #audit but the conversation didn't go anywhere. It would be nice if there could be some form of source code control for the changes that occur between revisions of the userspace tools. Is development internally to RedHat done using any form of source code control? Or is the development more ad-hoq? Full public source code control would perhaps be beneficial in terms of fostering community development. Failing this, just having the diffs per discret change included in each release would be very helpful. Possible? Thanks Tony