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 lvm2app.h
Date: Mon, 15 Feb 2010 19:55:00 -0000	[thread overview]
Message-ID: <20100215195549.19848.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	wysochanski@sourceware.org	2010-02-15 19:55:49

Modified files:
	liblvm         : lvm2app.h 

Log message:
	Update lvm2app.h comments to remove hidden VG comment list vgnames/vgids.
	
	Peter recently fixed lvm_list_vg_names() and lvm_list_vg_uuids() so they
	no longer return hidden names.  Remove the comment in lvm2app.h.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/liblvm/lvm2app.h.diff?cvsroot=lvm2&r1=1.10&r2=1.11

--- LVM2/liblvm/lvm2app.h	2010/02/14 03:21:38	1.10
+++ LVM2/liblvm/lvm2app.h	2010/02/15 19:55:49	1.11
@@ -281,8 +281,6 @@
  *
  * NOTE: This function normally does not scan devices in the system for LVM
  * metadata.  To scan the system, use lvm_scan.
- * NOTE: This function currently returns hidden VG names.  These names always
- * begin with a "#" and should be filtered out and not used.
  *
  * To process the list, use the dm_list iterator functions.  For example:
  *      vg_t vg;
@@ -315,8 +313,6 @@
  *
  * NOTE: This function normally does not scan devices in the system for LVM
  * metadata.  To scan the system, use lvm_scan.
- * NOTE: This function currently returns hidden VG names.  These names always
- * begin with a "#" and should be filtered out and not used.
  *
  * \param   libh
  * Handle obtained from lvm_init.


             reply	other threads:[~2010-02-15 19:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-15 19:55 wysochanski [this message]
2010-02-24 18:16 wysochanski
2010-07-12 18:29 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=20100215195549.19848.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).