From: Ian Jackson <ijackson@chiark.greenend.org.uk>
To: xen-devel@lists.xenproject.org
Cc: lars.kurth.xen@gmail.com, ian.jackson@eu.citrix.com,
Ian Jackson <ijackson@chiark.greenend.org.uk>
Subject: [PATCH SECURITY-POLICY 1/9] Grammar fix: Remove a comma splice
Date: Fri, 16 Jan 2015 19:52:13 +0000 [thread overview]
Message-ID: <1421437941-10997-1-git-send-email-ijackson@chiark.greenend.org.uk> (raw)
In-Reply-To: <21689.27383.339939.319567@chiark.greenend.org.uk>
No semantic change.
Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
---
security_vulnerability_process.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/security_vulnerability_process.html b/security_vulnerability_process.html
index 7069646..4ed0042 100644
--- a/security_vulnerability_process.html
+++ b/security_vulnerability_process.html
@@ -246,7 +246,7 @@ advisories. Please include in the e-mail:</p>
or have not sent a statement that they have read this policy and will
abide by, it will be asked to do so. </p>
<p>Organisations should not request subscription via the mailing list
-web interface, any such subscription requests will be rejected and
+web interface. Any such subscription requests will be rejected and
ignored.</p>
<p>A role address (such
as <a href="mailto:security@example.com">security@example.com</a>)
--
1.7.10.4
next prev parent reply other threads:[~2015-01-16 19:52 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 15:54 Security policy ambiguities - XSA-108 process post-mortem Xen Project Security Team
2014-10-08 23:06 ` Ian Jackson
2014-10-08 23:55 ` Lars Kurth
2014-10-09 9:37 ` Ian Jackson
2014-10-09 11:24 ` George Dunlap
2014-10-09 16:19 ` Ian Campbell
2014-10-10 14:25 ` Jan Beulich
2014-10-13 12:17 ` George Dunlap
2014-10-29 13:27 ` James Bulpin
2015-01-19 20:36 ` James McKenzie
2015-01-20 8:54 ` Jan Beulich
2015-01-20 12:29 ` George Dunlap
2015-02-12 10:44 ` Lars Kurth
2014-11-10 18:01 ` Ian Jackson
2014-11-11 12:39 ` John Haxby
2014-11-12 18:09 ` George Dunlap
2014-11-13 17:36 ` Ian Jackson
2014-11-14 12:10 ` Lars Kurth
2014-11-14 12:50 ` Ian Jackson
2014-11-14 17:37 ` Lars Kurth
2015-01-16 19:23 ` Ian Jackson
2015-01-16 19:48 ` [PATCH SECURITY-POLICY 0/9] " Ian Jackson
2015-01-16 19:52 ` Ian Jackson [this message]
2015-01-16 19:52 ` [PATCH SECURITY-POLICY 2/9] Add headings Ian Jackson
2015-01-16 19:52 ` [PATCH SECURITY-POLICY 3/9] Deployment with Security Team Permission Ian Jackson
2015-01-19 10:20 ` Jan Beulich
2015-01-19 11:18 ` Lars Kurth
2015-01-19 13:38 ` Ian Jackson
2015-01-19 14:25 ` Ian Campbell
2015-01-19 15:55 ` George Dunlap
2015-01-19 19:48 ` Lars Kurth
2015-01-19 12:36 ` Ian Campbell
2015-01-19 13:50 ` Jan Beulich
2015-01-19 12:35 ` Ian Campbell
2015-01-19 13:08 ` Ian Jackson
2015-01-19 13:10 ` Ian Campbell
2015-01-16 19:52 ` [PATCH SECURITY-POLICY 4/9] Use a public mailing list for predisclosure membership applications Ian Jackson
2015-01-19 12:49 ` Ian Campbell
2015-01-19 13:10 ` Ian Jackson
2015-01-19 13:19 ` Ian Campbell
2015-01-19 16:21 ` Don Koch
2015-01-19 17:57 ` Ian Jackson
2015-01-16 19:52 ` [PATCH SECURITY-POLICY 5/9] Tighten, and make more objective, predisclosure list application Ian Jackson
2015-01-16 19:52 ` [PATCH SECURITY-POLICY 6/9] Explicitly permit within-list information sharing during embargo Ian Jackson
2015-01-16 19:52 ` [PATCH SECURITY-POLICY 7/9] Clarify and fix prior consultation text Ian Jackson
2015-01-16 19:52 ` [PATCH SECURITY-POLICY 8/9] Clarify what announcements may be made by to service users Ian Jackson
2015-01-16 19:52 ` [PATCH SECURITY-POLICY 9/9] Document changes in changelog and heading Ian Jackson
2015-01-19 10:29 ` [PATCH SECURITY-POLICY 0/9] Re: Security policy ambiguities - XSA-108 process post-mortem Jan Beulich
2015-01-19 13:36 ` Ian Jackson
2015-01-19 19:45 ` Lars Kurth
2015-01-19 14:57 ` George Dunlap
2015-01-23 19:31 ` [PATCH v2 SECURITY-POLICY 0/9] " Ian Jackson
2015-01-23 19:31 ` [PATCH v2 SECURITY-POLICY 1/9] Grammar fix: Remove a comma splice Ian Jackson
2015-01-23 19:31 ` [PATCH v2 SECURITY-POLICY 2/9] Add headings Ian Jackson
2015-01-23 19:31 ` [PATCH v2 SECURITY-POLICY 3/9] Deployment with Security Team Permission Ian Jackson
2015-01-23 19:31 ` [PATCH v2 SECURITY-POLICY 4/9] Use a public mailing list for predisclosure membership applications Ian Jackson
2015-01-23 19:31 ` [PATCH v2 SECURITY-POLICY 5/9] Tighten, and make more objective, predisclosure list application Ian Jackson
2015-01-23 19:31 ` [PATCH v2 SECURITY-POLICY 6/9] Explicitly permit within-list information sharing during embargo Ian Jackson
2015-01-23 19:31 ` [PATCH v2 SECURITY-POLICY 7/9] Clarify and fix prior consultation text Ian Jackson
2015-01-23 19:31 ` [PATCH v2 SECURITY-POLICY 8/9] Clarify what announcements may be made by to service users Ian Jackson
2015-01-23 19:31 ` [PATCH v2 SECURITY-POLICY 9/9] Document changes in changelog and heading Ian Jackson
2015-02-02 17:27 ` [PATCH v2 SECURITY-POLICY 0/9] Security policy ambiguities - XSA-108 process post-mortem Ian Jackson
2015-02-03 9:49 ` Lars Kurth
2014-10-09 11:09 ` George Dunlap
2014-10-10 14:47 ` Jan Beulich
2014-10-13 11:23 ` George Dunlap
2014-10-13 12:16 ` Lars Kurth
2014-11-10 17:25 ` Ian Jackson
2014-10-29 13:27 ` James Bulpin
2014-11-10 17:21 ` Ian Jackson
2014-10-21 12:32 ` Ian Campbell
2014-10-21 14:31 ` Matt Wilson
2014-10-21 15:06 ` Jan Beulich
2014-11-10 17:29 ` Ian Jackson
2014-11-10 17:39 ` George Dunlap
2014-11-10 18:04 ` Ian Jackson
2014-10-30 11:58 ` Ian Jackson
2014-10-31 22:40 ` Matt Wilson
2014-11-03 11:37 ` George Dunlap
2014-11-03 17:23 ` Matt Wilson
2014-11-05 11:17 ` Ian Campbell
2014-11-06 16:01 ` Lars Kurth
2014-11-10 12:35 ` Ian Campbell
2014-10-22 23:23 ` Bastian Blank
2014-10-29 13:27 ` James Bulpin
2014-11-10 17:42 ` Ian Jackson
2014-10-09 8:29 ` Ian Campbell
2014-10-09 8:45 ` Processed: " xen
2014-10-29 13:27 ` James Bulpin
2014-10-30 10:51 ` Tim Deegan
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=1421437941-10997-1-git-send-email-ijackson@chiark.greenend.org.uk \
--to=ijackson@chiark.greenend.org.uk \
--cc=ian.jackson@eu.citrix.com \
--cc=lars.kurth.xen@gmail.com \
--cc=xen-devel@lists.xenproject.org \
/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.