public inbox for lvm2-cvs@sourceware.org
help / color / mirror / Atom feed
From: wysochanski@sourceware.org
To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org
Subject: LVM2/liblvm lvm.h
Date: Mon, 27 Jul 2009 08:28:00 -0000	[thread overview]
Message-ID: <20090727082813.21162.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	wysochanski@sourceware.org	2009-07-27 08:28:13

Modified files:
	liblvm         : lvm.h 

Log message:
	More liblvm header file cleanups.
	
	Author: Dave Wysochanski <dwysocha@redhat.com>

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/liblvm/lvm.h.diff?cvsroot=lvm2&r1=1.26&r2=1.27

--- LVM2/liblvm/lvm.h	2009/07/26 20:58:11	1.26
+++ LVM2/liblvm/lvm.h	2009/07/27 08:28:13	1.27
@@ -38,11 +38,11 @@
 /**
  * Physical volume object.
  *
- * This object can be either a read-only object or a read-write object
- * depending on the mode it was returned by a function. This object can not be
- * written to disk independently, it is bound to a volume group and changes
- * will be written to disk when the volume group gets committed to disk. The
- * open mode is the same as the volume group object is was created of.
+ * This object can be either a read-only object or a read-write object and
+ * depends on the mode of the volume group.  This object can not be
+ * written to disk independently, and changes will be written to disk
+ * when the volume group gets committed to disk. The open mode is the
+ * same as the volume group object it was created from.
  */
 typedef struct physical_volume pv_t;
 
@@ -60,10 +60,10 @@
  * Logical Volume object.
  *
  * This object can be either a read-only object or a read-write object
- * depending on the mode it was returned by a function. This object can not be
+ * depending on the mode of the volume group. This object can not be
  * written to disk independently, it is bound to a volume group and changes
  * will be written to disk when the volume group gets committed to disk. The
- * open mode is the same as the volume group object is was created of.
+ * open mode is the same as the volume group object is was created from.
  */
 typedef struct logical_volume lv_t;
 
@@ -287,7 +287,7 @@
 int lvm_vg_remove(vg_t *vg);
 
 /**
- * Close a VG opened with lvm_vg_create
+ * Close a VG opened with lvm_vg_create or lvm_vg_open.
  *
  * This API releases a VG handle and any resources associated with the handle.
  *


             reply	other threads:[~2009-07-27  8:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-27  8:28 wysochanski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-07-28 15:34 wysochanski
2009-07-28 12:19 wysochanski
2009-07-28  0:36 wysochanski
2009-07-27 21:13 wysochanski
2009-07-26 16:49 wysochanski
2009-07-26 16:35 wysochanski
2009-07-26 16:12 wysochanski
2009-07-23 23:37 wysochanski
2009-07-23 23:36 wysochanski

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=20090727082813.21162.qmail@sourceware.org \
    --to=wysochanski@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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).