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 lib/display/display.c
Date: Mon, 28 Sep 2009 16:36:00 -0000 [thread overview]
Message-ID: <20090928163604.28408.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: agk@sourceware.org 2009-09-28 16:36:03
Modified files:
. : WHATS_NEW
lib/display : display.c
Log message:
Treat input units of both 's' and 'S' as 512-byte sectors. (2.02.49)
's' and 'S' are special suffixes representing sectors and are always 512 bytes,
regardless of whether you're using powers of 1000 or 1024.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1274&r2=1.1275
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/display/display.c.diff?cvsroot=lvm2&r1=1.102&r2=1.103
--- LVM2/WHATS_NEW 2009/09/28 16:23:44 1.1274
+++ LVM2/WHATS_NEW 2009/09/28 16:36:03 1.1275
@@ -1,5 +1,6 @@
Version 2.02.54 -
=====================================
+ Treat input units of both 's' and 'S' as 512-byte sectors. (2.02.49)
Use standard output units for 'PE Size' and 'Stripe size' in pv/lvdisplay.
Add configure --enable-units-compat to set si_unit_consistency off by default.
Add global/si_unit_consistency to enable cleaned-up use of units in output.
--- LVM2/lib/display/display.c 2009/09/28 16:23:46 1.102
+++ LVM2/lib/display/display.c 2009/09/28 16:36:03 1.103
@@ -68,6 +68,7 @@
break;
#define KILO UINT64_C(1024)
case 's':
+ case 'S':
v *= (KILO/2);
break;
case 'k':
@@ -90,9 +91,6 @@
break;
#undef KILO
#define KILO UINT64_C(1000)
- case 'S':
- v *= (KILO/2);
- break;
case 'K':
v *= KILO;
break;
next reply other threads:[~2009-09-28 16:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-28 16:36 agk [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-02-13 14:23 zkabelac
2011-11-23 1:34 agk
2009-11-03 10:50 zkabelac
2009-09-30 14:19 agk
2007-05-31 14:19 wysochanski
2004-05-28 12:47 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=20090928163604.28408.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).