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 daemons/dmeventd/libdevmapper ... Date: Fri, 19 Mar 2010 18:33:00 -0000 [thread overview] Message-ID: <20100319183356.30453.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: agk@sourceware.org 2010-03-19 18:33:55 Modified files: . : WHATS_NEW daemons/dmeventd: libdevmapper-event.pc.in Log message: Fix libdevmapper-event pkgconfig version string to match libdevmapper. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1470&r2=1.1471 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/daemons/dmeventd/libdevmapper-event.pc.in.diff?cvsroot=lvm2&r1=1.1&r2=1.2 --- LVM2/WHATS_NEW 2010/03/18 17:32:25 1.1470 +++ LVM2/WHATS_NEW 2010/03/19 18:33:55 1.1471 @@ -1,5 +1,6 @@ Version 2.02.63 - ================================ + Fix libdevmapper-event pkgconfig version string to match libdevmapper. Avoid scanning all pvs in the system if operating on a device with mdas. Add configure --with-clvmd=singlenode to use clvmd w/o cluster infrastructure. Get stacktrace if testsuite test drops core and lvm was built with debugging. --- LVM2/daemons/dmeventd/libdevmapper-event.pc.in 2006/04/19 15:23:10 1.1 +++ LVM2/daemons/dmeventd/libdevmapper-event.pc.in 2010/03/19 18:33:55 1.2 @@ -5,7 +5,7 @@ Name: devmapper-event Description: device-mapper event library -Version: @DM_LIB_VERSION@ +Version: @DM_LIB_PATCHLEVEL@ Requires: devmapper Cflags: -I${includedir} Libs: -L${libdir} -ldevmapper-event
next reply other threads:[~2010-03-19 18:33 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-03-19 18:33 agk [this message] 2010-04-14 13:01 prajnoha 2010-05-11 8:47 zkabelac 2010-12-22 15:28 zkabelac 2012-02-28 11:03 zkabelac
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=20100319183356.30453.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: 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).