diff options
author | Thijs Kinkhorst <thijs@debian.org> | 2007-09-05 16:11:30 +0000 |
---|---|---|
committer | Thijs Kinkhorst <thijs@debian.org> | 2007-09-05 16:11:30 +0000 |
commit | e3abea9d003540160acf4c55bf07646a6dab6c59 (patch) | |
tree | 735606ff78c07c481ce431a76ad83f565d51f800 /doc | |
parent | 4fd97bba22a2b8bf4feca9a7214963a38b8ef9fb (diff) |
update docs
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@6514 e39458fd-73e7-0310-bf30-c45bca0a0e42
Diffstat (limited to 'doc')
-rw-r--r-- | doc/narrative_introduction | 7 | ||||
-rw-r--r-- | doc/testing-security | 6 |
2 files changed, 7 insertions, 6 deletions
diff --git a/doc/narrative_introduction b/doc/narrative_introduction index 52fb853c69..6938b83529 100644 --- a/doc/narrative_introduction +++ b/doc/narrative_introduction @@ -359,9 +359,10 @@ not blindly trust the script output and double-check it, though. Checking your changes --------------------- -After editing the lists in the data directory make sure to run -make check-syntax from the root of the svn directory to see if -the tracker is able to parse this file _before_ you commit it. +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 +the root of the svn directory. Following up on security issues ------------------------------- diff --git a/doc/testing-security b/doc/testing-security index aa718f5b49..845636e94d 100644 --- a/doc/testing-security +++ b/doc/testing-security @@ -16,7 +16,7 @@ The initial goals of the Debian testing security team will be to: Existing infrastructure The main infrastructure we have that could be useful in preparing testing -secrity updates is the testing-proposed-updates queue. Thanks to the recent +security updates is the testing-proposed-updates queue. Thanks to the recent work on the sarge release, t-p-u is functional for all (or almost all) arches. @@ -26,7 +26,7 @@ with upstream security sources, etc. There is the Debian BTS, which contains some but not all details about security holes in Debian. Some security holes are not made public until a DSA is released, and some are silently fixed in a new upstream release -uploaded to unstable. The BTS has some isues with keeping track of which +uploaded to unstable. The BTS has some issues with keeping track of which bugs apply to testing, though its developers have been working on solving this problem for a while. @@ -49,7 +49,7 @@ available on security.debian.org the same as stable security updates. There will be an apt repository for testing security updates, similar to security.debian.org. Uploads to this repository will be made only by members of the testing security team, will be GPG signed in the usual way, -and will be accomponied a DTSA (Debian Testing Security Advisory), posted +and will be accompanied a DTSA (Debian Testing Security Advisory), posted to our web site, and to a mailing list. In the very early stages, this will only include security updates for the |