From fbf2fa4f7c15cfcde273e35cbc5ff2f9e7289043 Mon Sep 17 00:00:00 2001 From: =?utf8?q?J=C3=A9r=C3=A9mie=20Galarneau?= Date: Fri, 15 Mar 2013 17:36:05 -0400 Subject: [PATCH] Typo fix in the tracers requirements MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit Signed-off-by: Jérémie Galarneau Signed-off-by: Mathieu Desnoyers --- common-trace-format-reqs.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/common-trace-format-reqs.txt b/common-trace-format-reqs.txt index 66fe55a..e5e7c7a 100644 --- a/common-trace-format-reqs.txt +++ b/common-trace-format-reqs.txt @@ -268,7 +268,7 @@ Enumerating these higher-level requirements influence the trace format in many ways. For instance, a requirement for compactness leads to schemes where all information repetition should be eliminated. Thus the need for optional per-section context information. Another example is the requirement for speed -and streaming. The requirement for speed ans treaming leads to zero-copy +and streaming. The requirement for speed and streaming leads to zero-copy implementations, which imply that the trace format should be written natively by the tracer. The tracer requirements stated in this section are stated to ensure that the trace format structure makes it possible for a tracer to cope with the -- 2.34.1