From mboxrd@z Thu Jan  1 00:00:00 1970
From: Tony Jones <tonyj@suse.de>
Subject: Re: source code control for audit userspace tools
Date: Thu, 15 Feb 2007 11:00:56 -0800
Message-ID: <20070215190056.GA9852@suse.de>
References: <20070215000608.GA17782@suse.de>
	<200702151544.l1FFiTR2021164@turing-police.cc.vt.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <linux-audit-bounces@redhat.com>
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 l1FJ1uHv027153
	for <linux-audit@redhat.com>; Thu, 15 Feb 2007 14:01:56 -0500
Received: from mx2.suse.de (ns2.suse.de [195.135.220.15])
	by mx1.redhat.com (8.13.1/8.13.1) with ESMTP id l1FJ1qu3006311
	for <linux-audit@redhat.com>; Thu, 15 Feb 2007 14:01:53 -0500
Content-Disposition: inline
In-Reply-To: <200702151544.l1FFiTR2021164@turing-police.cc.vt.edu>
List-Unsubscribe: <https://www.redhat.com/mailman/listinfo/linux-audit>,
	<mailto:linux-audit-request@redhat.com?subject=unsubscribe>
List-Archive: <https://www.redhat.com/archives/linux-audit>
List-Post: <mailto:linux-audit@redhat.com>
List-Help: <mailto:linux-audit-request@redhat.com?subject=help>
List-Subscribe: <https://www.redhat.com/mailman/listinfo/linux-audit>,
	<mailto:linux-audit-request@redhat.com?subject=subscribe>
Sender: linux-audit-bounces@redhat.com
Errors-To: linux-audit-bounces@redhat.com
To: Valdis.Kletnieks@vt.edu
Cc: linux-audit@redhat.com
List-Id: linux-audit@redhat.com

On Thu, Feb 15, 2007 at 10:44:29AM -0500, Valdis.Kletnieks@vt.edu wrote:
> On Wed, 14 Feb 2007 16:06:08 PST, Tony Jones said:
> > 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?
> 
> A publicly accessible git tree would be nice. :)
> 
> (Of course, that's only if 'git' is the native storage, or if there's a
> per-commit export to it - a git repository that has a changelog that
> reads 'import 1.1.3', 'import 1.1.4', etc isn't much help....)

Right, it needs to be per discrete change (feature and bugfix) which clearly
may have an impact on how internal development is done.

I don't care if it's git, svn, cvs or just a directory per release containing
a set of discrete patches.

Unless there is some scc inside of redhat, I'm guessing it's too late for
past releases and this will just be for going forward.

Thanks!

Tony