public inbox for lvm2-cvs@sourceware.org help / color / mirror / Atom feed
From: agk@sourceware.org To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org Subject: LVM2 VERSION WHATS_NEW Date: Fri, 01 Dec 2006 23:16:00 -0000 [thread overview] Message-ID: <20061201231600.12618.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: agk@sourceware.org 2006-12-01 23:16:00 Modified files: . : VERSION WHATS_NEW Log message: pre release Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/VERSION.diff?cvsroot=lvm2&r1=1.131&r2=1.132 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.513&r2=1.514 --- LVM2/VERSION 2006/11/21 17:46:11 1.131 +++ LVM2/VERSION 2006/12/01 23:15:59 1.132 @@ -1 +1 @@ -2.02.16-cvs (2006-11-21) +2.02.16-cvs (2006-12-01) --- LVM2/WHATS_NEW 2006/12/01 22:48:47 1.513 +++ LVM2/WHATS_NEW 2006/12/01 23:15:59 1.514 @@ -1,5 +1,5 @@ -Version 2.02.16 - -==================================== +Version 2.02.16 - 1st December 2006 +=================================== Fix VG clustered read locks to use PR not CR. Adjust some alignments for ia64/sparc. Fix mirror segment removal to use temporary error segment.
next reply other threads:[~2006-12-01 23:16 UTC|newest] Thread overview: 122+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-12-01 23:16 agk [this message] -- strict thread matches above, loose matches on Subject: below -- 2011-01-24 23:34 agk 2011-01-17 16:46 agk 2010-04-19 15:24 wysochanski 2009-07-28 17:07 agk 2008-10-26 10:40 agk 2008-10-17 17:48 agk 2008-10-17 17:42 agk 2008-09-19 6:48 agk 2008-06-27 22:35 agk 2008-06-27 21:56 agk 2008-06-11 12:14 agk 2008-06-11 12:08 agk 2008-04-15 15:01 agk 2008-04-15 14:49 agk 2008-04-10 20:07 agk 2008-04-10 18:19 agk 2008-01-31 12:41 agk 2008-01-31 12:37 agk 2008-01-29 12:02 agk 2008-01-29 11:48 agk 2008-01-19 12:30 agk 2008-01-19 12:28 agk 2008-01-17 15:03 agk 2007-12-05 22:48 agk 2007-12-05 22:19 agk 2007-08-24 21:05 agk 2007-07-17 20:53 agk 2007-07-17 20:45 agk 2007-06-15 19:05 agk 2007-04-27 20:58 agk 2007-03-19 21:16 agk 2007-03-19 21:12 agk 2007-03-08 21:37 agk 2007-03-08 21:28 agk 2007-02-13 16:10 agk 2007-02-13 16:04 agk 2007-01-30 21:37 agk 2007-01-30 18:08 agk 2007-01-25 23:40 agk 2007-01-25 23:37 agk 2007-01-17 17:56 agk 2007-01-17 17:51 agk 2007-01-11 23:17 agk 2007-01-11 22:49 agk 2006-12-14 22:21 agk 2006-12-14 20:05 agk 2006-12-01 23:29 agk 2006-11-20 23:30 agk 2006-11-20 19:33 agk 2006-11-10 21:27 agk 2006-11-10 21:22 agk 2006-10-27 15:37 agk 2006-10-27 15:21 agk 2006-10-12 18:13 agk 2006-09-19 19:37 agk 2006-09-19 19:15 agk 2006-08-17 20:04 agk 2006-08-17 19:55 agk 2006-08-15 19:13 agk 2006-08-15 19:06 agk 2006-07-17 14:39 agk 2006-07-17 14:32 agk 2006-05-12 20:32 agk 2006-05-12 19:41 agk 2006-04-19 20:15 agk 2006-04-19 18:06 agk 2006-04-14 21:39 agk 2006-04-14 21:11 agk 2006-02-07 16:33 agk 2005-11-23 18:45 agk 2005-11-23 18:42 agk 2005-11-10 16:06 agk 2005-11-10 15:27 agk 2005-10-16 20:09 agk 2005-10-16 20:06 agk 2005-08-04 2:07 agk 2005-07-13 19:28 agk 2005-07-13 19:15 agk 2005-06-14 18:22 agk 2005-06-14 17:59 agk 2005-06-13 14:53 agk 2005-05-09 16:42 agk 2005-04-04 15:46 agk 2005-04-04 15:41 agk 2005-03-22 16:50 agk 2005-03-22 15:12 agk 2005-03-10 20:22 agk 2005-03-03 22:31 agk 2005-03-03 22:26 agk 2005-02-18 19:06 agk 2005-02-09 18:26 agk 2005-02-09 17:49 agk 2005-02-01 16:40 agk 2005-02-01 16:29 agk 2005-01-21 19:03 agk 2005-01-21 18:49 agk 2005-01-17 20:45 agk 2005-01-07 20:06 agk 2005-01-07 19:50 agk 2004-12-22 22:04 agk 2004-12-12 21:55 agk 2004-12-12 21:47 agk 2004-12-10 18:01 agk 2004-12-10 16:02 agk 2004-11-27 22:56 agk 2004-11-23 18:36 agk 2004-11-23 17:47 agk 2004-09-29 15:25 agk 2004-09-29 15:07 agk 2004-09-16 21:48 agk 2004-09-16 20:56 agk 2004-09-15 15:59 agk 2004-09-03 19:18 agk 2004-08-19 17:13 agk 2004-08-19 16:10 agk 2004-07-03 18:29 agk 2004-06-29 13:46 agk 2004-05-24 19:21 agk 2004-04-14 20:09 agk 2004-04-08 17:14 agk 2004-04-06 15:18 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=20061201231600.12618.qmail@sourceware.org \ --to=agk@sourceware.org \ --cc=lvm-devel@redhat.com \ --cc=lvm2-cvs@sourceware.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).