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 lib/report/columns.h lib/repo ... Date: Tue, 11 Sep 2007 13:49:00 -0000 [thread overview] Message-ID: <20070911134952.5800.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: wysochanski@sourceware.org 2007-09-11 13:49:52 Modified files: . : WHATS_NEW lib/report : columns.h report.c Log message: Undo previous checkin - output format not good, info already available in other form(s) Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.703&r2=1.704 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/report/columns.h.diff?cvsroot=lvm2&r1=1.22&r2=1.23 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/report/report.c.diff?cvsroot=lvm2&r1=1.62&r2=1.63 --- LVM2/WHATS_NEW 2007/09/10 20:05:29 1.703 +++ LVM2/WHATS_NEW 2007/09/11 13:49:51 1.704 @@ -1,6 +1,5 @@ Version 2.02.29 - ================================== - Add pvseg_free field to 'pvs' output. Include strerror string in dev_open_flags' stat failure message. Move guts of pvresize into library. Avoid error when --corelog is provided without --mirrorlog. (2.02.28) --- LVM2/lib/report/columns.h 2007/09/10 20:05:29 1.22 +++ LVM2/lib/report/columns.h 2007/09/11 13:49:51 1.23 @@ -83,5 +83,4 @@ FIELD(PVSEGS, pvseg, NUM, "Start", pe, 5, uint32, "pvseg_start", "Physical Extent number of start of segment.") FIELD(PVSEGS, pvseg, NUM, "SSize", len, 5, uint32, "pvseg_size", "Number of extents in segment.") -FIELD(PVSEGS, pvseg, STR, "Free", lvseg, 5, lvseg, "pvseg_free", "Whether the segment is free or allocated to an LV.") /* *INDENT-ON* */ --- LVM2/lib/report/report.c 2007/09/10 20:05:29 1.62 +++ LVM2/lib/report/report.c 2007/09/11 13:49:52 1.63 @@ -62,15 +62,6 @@ /* * Data-munging functions to prepare each data type for display and sorting */ -static int _lvseg_disp(struct dm_report *rh, struct dm_pool *mem __attribute((unused)), - struct dm_report_field *field, - const void *data, void *private __attribute((unused))) -{ - const struct lv_segment *seg = *(const struct lv_segment **) data; - dm_report_field_set_value(field, seg ? "N" : "Y", NULL); - return 1; -} - static int _string_disp(struct dm_report *rh, struct dm_pool *mem __attribute((unused)), struct dm_report_field *field, const void *data, void *private __attribute((unused)))
next reply other threads:[~2007-09-11 13:49 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-09-11 13:49 wysochanski [this message] -- strict thread matches above, loose matches on Subject: below -- 2010-06-23 12:32 agk 2009-02-09 9:45 mbroz 2007-09-10 20:05 wysochanski 2007-07-09 15:40 agk 2005-09-23 17:06 agk 2005-08-15 23:34 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=20070911134952.5800.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: linkBe 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).