public inbox for lvm2-cvs@sourceware.org help / color / mirror / Atom feed
From: zkabelac@sourceware.org To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org Subject: LVM2 Makefile.in WHATS_NEW Date: Wed, 01 Feb 2012 10:46:00 -0000 [thread overview] Message-ID: <20120201104648.29780.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: zkabelac@sourceware.org 2012-02-01 10:46:46 Modified files: . : Makefile.in WHATS_NEW Log message: User correct base dir for lcov reports Fix problem when srcdir != builddir. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/Makefile.in.diff?cvsroot=lvm2&r1=1.67&r2=1.68 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.2249&r2=1.2250 --- LVM2/Makefile.in 2011/11/23 12:21:41 1.67 +++ LVM2/Makefile.in 2012/02/01 10:46:45 1.68 @@ -116,7 +116,7 @@ # maybe use subdirs processing to create tracefiles... $(LCOV_TRACES): - $(LCOV) -b $(top_srcdir)/$(basename $@) \ + $(LCOV) -b $(basename $@) \ -d $(basename $@) -c -o - | $(SED) \ -e "s/\(dmeventd_lvm.[ch]\)/plugins\/lvm2\/\1/" \ -e "s/\(dmeventd_mirror.c\)/plugins\/mirror\/\1/" \ --- LVM2/WHATS_NEW 2012/02/01 02:10:45 1.2249 +++ LVM2/WHATS_NEW 2012/02/01 10:46:45 1.2250 @@ -1,5 +1,6 @@ Version 2.02.90 - =================================== + Fix lcov reports when srcdir != builddir. Allow ALLOC_NORMAL to track reserved extents for log and data on same PV. Automatically detect whether corosync clvmd needs to use confdb or cmap. Fix data% report for thin volume used as origin for non-thin snapshot.
next reply other threads:[~2012-02-01 10:46 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-01 10:46 zkabelac [this message] -- strict thread matches above, loose matches on Subject: below -- 2012-03-23 9:39 zkabelac 2010-11-22 21:39 agk 2010-08-02 13:56 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=20120201104648.29780.qmail@sourceware.org \ --to=zkabelac@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).