From: Tony Jones <tonyj@suse.de>
To: linux-audit@redhat.com
Subject: source code control for audit userspace tools
Date: Wed, 14 Feb 2007 16:06:08 -0800 [thread overview]
Message-ID: <20070215000608.GA17782@suse.de> (raw)
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
next reply other threads:[~2007-02-15 0:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 0:06 Tony Jones [this message]
2007-02-15 11:48 ` source code control for audit userspace tools Steve Grubb
2007-02-15 15:44 ` Valdis.Kletnieks
2007-02-15 19:00 ` Tony Jones
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=20070215000608.GA17782@suse.de \
--to=tonyj@suse.de \
--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