From: meyering@sourceware.org <meyering@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2 ./WHATS_NEW tools/lvmcmdline.c
Date: 21 Sep 2007 18:06:56 -0000 [thread overview]
Message-ID: <20070921180656.21738.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: meyering at sourceware.org 2007-09-21 18:06:56
Modified files:
. : WHATS_NEW
tools : lvmcmdline.c
Log message:
Print --help output to stdout, not stderr.
* tools/lvmcmdline.c (_usage): Use log_print, not log_error.
Author: Jim Meyering <jim@meyering.net>
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.712&r2=1.713
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/tools/lvmcmdline.c.diff?cvsroot=lvm2&r1=1.50&r2=1.51
--- LVM2/WHATS_NEW 2007/09/21 18:06:33 1.712
+++ LVM2/WHATS_NEW 2007/09/21 18:06:56 1.713
@@ -1,5 +1,6 @@
Version 2.02.29 -
==================================
+ All tools: print --help output to stdout, not stderr.
After a diagnostic, suggest --help, rather than printing all --help output.
Add %PVS extents option to lvresize, lvextend, and lvcreate.
Moved the obsolete test subdirectory to old-tests.
--- LVM2/tools/lvmcmdline.c 2007/09/21 18:06:33 1.50
+++ LVM2/tools/lvmcmdline.c 2007/09/21 18:06:56 1.51
@@ -478,7 +478,7 @@
if (!com)
return;
- log_error("%s: %s\n\n%s", com->name, com->desc, com->usage);
+ log_print("%s: %s\n\n%s", com->name, com->desc, com->usage);
}
/*
next reply other threads:[~2007-09-21 18:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-21 18:06 meyering [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-09-16 12:10 LVM2 ./WHATS_NEW tools/lvmcmdline.c zkabelac
2010-11-24 9:53 zkabelac
2010-09-30 11:44 zkabelac
2010-06-30 16:43 agk
2010-02-15 16:26 prajnoha
2008-12-19 14:43 prajnoha
2008-12-19 14:49 ` Alasdair G Kergon
2008-01-09 15:55 mornfall
2007-09-21 18:06 meyering
2006-11-14 15:28 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=20070921180656.21738.qmail@sourceware.org \
--to=meyering@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.