Re: [Secure-testing-commits] r16971 - bin

[Johnathan Ritzi <jrdioko@gmail.com>]

How's this?

Index: doc/narrative_introduction
===================================================================
--- doc/narrative_introduction    (revision 16973)
+++ doc/narrative_introduction    (working copy)

@@ -441,9 +441,16 @@
 There is a script running, which automatically commits them to DSA/list.
 In some cases it needs manual fixups.
 
-Checking your changes
----------------------
+Checking in your changes

+------------------------
 
+After thoroughly researching each issue and editing the relevant files,
+commit your changes. Peer review is done via the mailing list and IRC
+notifications (see "Automatic Issue Updates" above). However, changes to

+the tracker website itself (e.g. the files in bin/) should be vetted and
+approved before being committed. The preferred way to do this is to send
+a patch to the debian-security-tracker@lists.debian.org mailing list.

+
 Commits are checked for syntax errors before they are actually committed,
 and you'll receive an error and your commit is aborted if it is in error.
 To check your changes yourself beforehand, use "make check-syntax" from

On Fri, Jul 22, 2011 at 11:10 PM, Michael Gilbert <michael.s.gilbert@gmail.com> wrote:

Johnathan Ritzi wrote:

> Understood. That would be something good to mention in that Introduction
> document for new members as well.

Feel free to add that since you have commit access now.

Best wishes,
Mike

_______________________________________________
Secure-testing-commits mailing list
Secure-testing-commits@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/secure-testing-commits