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 ./WHATS_NEW tools/vgreduce.c
Date: Wed, 31 Jan 2007 16:26:00 -0000 [thread overview]
Message-ID: <20070131162623.18518.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: agk@sourceware.org 2007-01-31 16:26:23
Modified files:
. : WHATS_NEW
tools : vgreduce.c
Log message:
Fix some &->&& vgreduce cmdline validation. [Andre Noll]
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.568&r2=1.569
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/tools/vgreduce.c.diff?cvsroot=lvm2&r1=1.55&r2=1.56
--- LVM2/WHATS_NEW 2007/01/30 21:37:18 1.568
+++ LVM2/WHATS_NEW 2007/01/31 16:26:22 1.569
@@ -1,5 +1,6 @@
Version 2.02.22 -
===================================
+ Fix some vgreduce --removemissing command line validation.
Version 2.02.21 - 30th January 2007
===================================
--- LVM2/tools/vgreduce.c 2007/01/09 23:14:34 1.55
+++ LVM2/tools/vgreduce.c 2007/01/31 16:26:23 1.56
@@ -427,13 +427,13 @@
int ret = 1;
int consistent = 1;
- if (!argc & !arg_count(cmd, removemissing_ARG)) {
+ if (!argc && !arg_count(cmd, removemissing_ARG)) {
log_error("Please give volume group name and "
"physical volume paths");
return EINVALID_CMD_LINE;
}
- if (!argc & arg_count(cmd, removemissing_ARG)) {
+ if (!argc && arg_count(cmd, removemissing_ARG)) {
log_error("Please give volume group name");
return EINVALID_CMD_LINE;
}
next reply other threads:[~2007-01-31 16:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 16:26 agk [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-30 14:59 zkabelac
2006-09-07 23:23 agk
2005-12-21 18:51 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=20070131162623.18518.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: 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).