From: david.goulet@polymtl.ca (David Goulet)
Subject: [ltt-dev] [PATCH] Updates Changelog for UST version 0.6
Date: Tue, 17 Aug 2010 14:47:00 -0400 [thread overview]
Message-ID: <1282070820-24647-1-git-send-email-david.goulet@polymtl.ca> (raw)
Signed-off-by: David Goulet <david.goulet at polymtl.ca>
---
ChangeLog | 11 +++++++++++
1 files changed, 11 insertions(+), 0 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index 7c0f74a..30035ef 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,14 @@
+2010-08-16 ust 0.6
+ * add ust strncpy interface for input robustness
+ * multiple memory barrier fix
+ * add libustd: contains the core functionality of ustd
+ * add get/set commands for daemon socket path
+ * fix cacheline aligned to use liburcu value
+ * fix usage of custom probes: use trace_mark_tp
+ * remove ltt_relay_buffer_flush function
+ * add ustctl manpage: force-switch and get/set-sock-path
+ * fix invalid array size and directory creation mode for ustd
+
2010-06-30 ust 0.5
* add support for PowerPC 32 architecture
* use clock_gettime(CLOCK_MONOTINIC) instead of gettimeofday()
--
1.7.0.4
next reply other threads:[~2010-08-17 18:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 18:47 David Goulet [this message]
2010-08-17 18:52 ` Mathieu Desnoyers
2010-08-20 3:48 ` Pierre-Marc Fournier
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=1282070820-24647-1-git-send-email-david.goulet@polymtl.ca \
--to=david.goulet@polymtl.ca \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox