From: Valdis.Kletnieks@vt.edu
To: Tony Jones <tonyj@suse.de>
Cc: linux-audit@redhat.com
Subject: Re: source code control for audit userspace tools
Date: Thu, 15 Feb 2007 10:44:29 -0500 [thread overview]
Message-ID: <200702151544.l1FFiTR2021164@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Wed, 14 Feb 2007 16:06:08 PST." <20070215000608.GA17782@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 570 bytes --]
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....)
[-- Attachment #1.2: Type: application/pgp-signature, Size: 226 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2007-02-15 15:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 0:06 source code control for audit userspace tools Tony Jones
2007-02-15 11:48 ` Steve Grubb
2007-02-15 15:44 ` Valdis.Kletnieks [this message]
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=200702151544.l1FFiTR2021164@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=linux-audit@redhat.com \
--cc=tonyj@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.