From: agk@sourceware.org
To: dm-cvs@sourceware.org, dm-devel@redhat.com
Subject: device-mapper VERSION WHATS_NEW
Date: 6 Jun 2008 19:09:20 -0000 [thread overview]
Message-ID: <20080606190920.10589.qmail@sourceware.org> (raw)
CVSROOT: /cvs/dm
Module name: device-mapper
Changes by: agk@sourceware.org 2008-06-06 19:09:20
Modified files:
. : VERSION WHATS_NEW
Log message:
pre-release
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/device-mapper/VERSION.diff?cvsroot=dm&r1=1.134&r2=1.135
http://sourceware.org/cgi-bin/cvsweb.cgi/device-mapper/WHATS_NEW.diff?cvsroot=dm&r1=1.235&r2=1.236
--- device-mapper/VERSION 2008/04/10 18:04:31 1.134
+++ device-mapper/VERSION 2008/06/06 19:09:19 1.135
@@ -1 +1 @@
-1.02.26-cvs (2008-04-10)
+1.02.26-cvs (2008-06-06)
--- device-mapper/WHATS_NEW 2008/06/06 18:53:26 1.235
+++ device-mapper/WHATS_NEW 2008/06/06 19:09:19 1.236
@@ -1,5 +1,5 @@
-Version 1.02.26 -
-=================================
+Version 1.02.26 - 6th June 2008
+===============================
Initialise params buffer to empty string in _emit_segment.
Skip add_dev_node when ioctls disabled.
Make dm_hash_iter safe against deletion.
next reply other threads:[~2008-06-06 19:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 19:09 agk [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-18 20:09 device-mapper VERSION WHATS_NEW agk
2008-06-25 14:44 agk
2008-06-06 19:22 agk
2008-04-10 18:04 agk
2008-04-10 18:00 agk
2007-12-20 15:16 agk
2007-12-20 15:12 agk
2007-12-05 17:14 agk
2007-08-21 17:03 agk
2007-08-21 16:33 agk
2007-07-13 16:10 agk
2007-07-13 16:07 agk
2007-06-15 20:49 agk
2007-06-15 18:40 agk
2007-04-27 20:09 agk
2007-04-27 19:47 agk
2007-02-13 16:16 agk
2007-02-13 16:12 agk
2007-01-29 20:25 agk
2007-01-25 23:36 agk
2007-01-25 23:33 agk
2007-01-17 17:50 agk
2007-01-17 17:47 agk
2007-01-11 23:19 agk
2007-01-11 22:44 agk
2006-11-28 22:51 agk
2006-11-28 22:49 agk
2006-10-13 18:43 agk
2006-10-12 17:45 agk
2006-10-12 17:37 agk
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=20080606190920.10589.qmail@sourceware.org \
--to=agk@sourceware.org \
--cc=dm-cvs@sourceware.org \
--cc=dm-devel@redhat.com \
/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