You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by br...@apache.org on 2015/12/06 00:28:02 UTC
svn commit: r1718135 - /subversion/trunk/tools/dist/README.advisory
Author: brane
Date: Sat Dec 5 23:28:02 2015
New Revision: 1718135
URL: http://svn.apache.org/viewvc?rev=1718135&view=rev
Log:
* tools/dist/README.advisory: Duh; can't make a single commit without typos.
Modified:
subversion/trunk/tools/dist/README.advisory
Modified: subversion/trunk/tools/dist/README.advisory
URL: http://svn.apache.org/viewvc/subversion/trunk/tools/dist/README.advisory?rev=1718135&r1=1718134&r2=1718135&view=diff
==============================================================================
--- subversion/trunk/tools/dist/README.advisory (original)
+++ subversion/trunk/tools/dist/README.advisory Sat Dec 5 23:28:02 2015
@@ -13,11 +13,11 @@ Step 2: Prepare the website update
$ cd ${PMC_AREA_WC}/security
$ ${TRUNK_WC}/tools/dist/advisory.py generate \
- --destinatio=${SITE_WC}/publish/security \
+ --destination=${SITE_WC}/publish/security \
CVE-2015-5259 CVE-2015-5343 ...
This will generate a plain-text version of the advisories, including
-patches etc., suiatble for publishing on our web site. Once these
+patches etc., suitable for publishing on our web site. Once these
are generated, make sure you add the links to the new files to:
${SITE_WC}/publish/security/index.html
@@ -54,11 +54,11 @@ Note the arguments:
----------------------
-Step 4: Send teh mails
+Step 4: Send the mails
----------------------
$ cd ${PMC_AREA_WC}/security
- $ ${TRUNK_WC}/tools/dist/advisory.py test \
+ $ ${TRUNK_WC}/tools/dist/advisory.py send \
(the rest of the arguments are as in step 3).
The mails will be sent one at a time to each recipient separately.