[PATCH ctf] Typo fix in the tracers requirements

[PATCH ctf] Typo fix in the tracers requirements

[Jérémie Galarneau]

Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>
---
 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
-- 
1.8.1.5


_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

Re: [PATCH ctf] Typo fix in the tracers requirements

[Mathieu Desnoyers]

* Jérémie Galarneau (jeremie.galarneau@efficios.com) wrote:
> Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>

merged, thanks!

Mathieu

> ---
>  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
> -- 
> 1.8.1.5
> 
> 
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com