All of lore.kernel.org
 help / color / mirror / Atom feed
From: agk@sourceware.org <agk@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2 ./WHATS_NEW man/lvm.8.in
Date: 26 Apr 2012 15:24:48 -0000	[thread overview]
Message-ID: <20120426152448.8914.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	agk at sourceware.org	2012-04-26 15:24:47

Modified files:
	.              : WHATS_NEW 
	man            : lvm.8.in 

Log message:
	Remove statement that snapshots cannot be tagged from lvm man page.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.2393&r2=1.2394
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/man/lvm.8.in.diff?cvsroot=lvm2&r1=1.10&r2=1.11

--- LVM2/WHATS_NEW	2012/04/25 13:38:41	1.2393
+++ LVM2/WHATS_NEW	2012/04/26 15:24:46	1.2394
@@ -1,5 +1,6 @@
 Version 2.02.96 - 
 ================================
+  Remove statement that snapshots cannot be tagged from lvm man page.
   Disallow changing cluster attribute of VG while RAID LVs are active.
   Fix lvconvert error message for non-mergeable volumes.
   Allow subset of failed devices to be replaced in RAID LVs.
--- LVM2/man/lvm.8.in	2012/04/11 12:42:10	1.10
+++ LVM2/man/lvm.8.in	2012/04/26 15:24:46	1.11
@@ -223,7 +223,6 @@
 Only the new LVM2 metadata format supports tagging: objects using the
 LVM1 metadata format cannot be tagged because the on-disk format does not
 support it.
-Snapshots cannot be tagged.
 Characters allowed in tags are:
 .B A-Z a-z 0-9 _ + . -
 and as of version 2.02.78 the following characters are also accepted:



             reply	other threads:[~2012-04-26 15:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26 15:24 agk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-03-01 10:39 LVM2 ./WHATS_NEW man/lvm.8.in zkabelac
2009-02-20  1:47 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=20120426152448.8914.qmail@sourceware.org \
    --to=agk@sourceware.org \
    --cc=lvm-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 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.