All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jérémie Galarneau" <jeremie.galarneau@efficios.com>
To: lttng-dev@lists.lttng.org
Subject: [PATCH ctf] Typo fix in the tracers requirements
Date: Fri, 15 Mar 2013 17:16:04 -0400	[thread overview]
Message-ID: <1363382164-12487-1-git-send-email-jeremie.galarneau__47735.33936027$1363382237$gmane$org@efficios.com> (raw)

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

             reply	other threads:[~2013-03-15 21:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-15 21:16 Jérémie Galarneau [this message]
     [not found] <1363382164-12487-1-git-send-email-jeremie.galarneau@efficios.com>
2013-03-15 21:37 ` [PATCH ctf] Typo fix in the tracers requirements Mathieu Desnoyers

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='1363382164-12487-1-git-send-email-jeremie.galarneau__47735.33936027$1363382237$gmane$org@efficios.com' \
    --to=jeremie.galarneau@efficios.com \
    --cc=lttng-dev@lists.lttng.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.