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 ./WHATS_NEW tools/vgdisplay.c
Date: Fri, 07 Nov 2008 19:02:00 -0000	[thread overview]
Message-ID: <20081107190247.11990.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	wysochanski@sourceware.org	2008-11-07 19:02:47

Modified files:
	.              : WHATS_NEW 
	tools          : vgdisplay.c 

Log message:
	Fix vgdisplay return code and exit status.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.990&r2=1.991
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/tools/vgdisplay.c.diff?cvsroot=lvm2&r1=1.21&r2=1.22

--- LVM2/WHATS_NEW	2008/11/03 18:59:58	1.990
+++ LVM2/WHATS_NEW	2008/11/07 19:02:47	1.991
@@ -1,5 +1,6 @@
 Version 2.02.43 -
 ===================================
+  Fix vgdisplay return code and exit status.
   Move list.c into libdevmapper and rename functions.
   Rename a couple of variables that matched function names.
   Use simplified x.y.z version number in libdevmapper.pc.
--- LVM2/tools/vgdisplay.c	2008/06/10 20:07:04	1.21
+++ LVM2/tools/vgdisplay.c	2008/11/07 19:02:47	1.22
@@ -98,8 +98,8 @@
 	}
 **********/
 
-	process_each_vg(cmd, argc, argv, LCK_VG_READ, 0, NULL,
-			vgdisplay_single);
+	return process_each_vg(cmd, argc, argv, LCK_VG_READ, 0, NULL,
+			       vgdisplay_single);
 
 /******** FIXME Need to count number processed
 	  Add this to process_each_vg if arg_count(cmd,activevolumegroups_ARG) ?
@@ -112,6 +112,4 @@
 		return LVM_E_NO_VG;
 	}
 ************/
-
-	return ECMD_PROCESSED;
 }


                 reply	other threads:[~2008-11-07 19:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20081107190247.11990.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).