From: wysochanski@sourceware.org <wysochanski@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2 ./WHATS_NEW lib/log/log.c
Date: 17 Jun 2008 14:14:01 -0000 [thread overview]
Message-ID: <20080617141401.17414.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: wysochanski at sourceware.org 2008-06-17 14:14:00
Modified files:
. : WHATS_NEW
lib/log : log.c
Log message:
Fix identifier 'error_message_produced' used ambiguously.
Related compiler warning:
log/log.c:242: warning: declaration of 'error_message_produced' shadows a global declaration
../include/log.h:98: warning: shadowed declaration is here
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.904&r2=1.905
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/log/log.c.diff?cvsroot=lvm2&r1=1.46&r2=1.47
--- LVM2/WHATS_NEW 2008/06/13 14:37:15 1.904
+++ LVM2/WHATS_NEW 2008/06/17 14:14:00 1.905
@@ -1,5 +1,6 @@
Version 2.02.39 -
================================
+ Fix ambiguous use of identifier 'error_message_produced'.
Begin syncing configure.in for merge/unification with device-mapper.
Fix add_mirror_images not to dereference uninitialized log_lv upon failure.
Don't call openlog for every debug line output by clvmd.
--- LVM2/lib/log/log.c 2008/06/06 19:28:33 1.46
+++ LVM2/lib/log/log.c 2008/06/17 14:14:00 1.47
@@ -239,9 +239,9 @@
_indent = indent;
}
-void init_error_message_produced(int error_message_produced)
+void init_error_message_produced(int value)
{
- _error_message_produced = error_message_produced;
+ _error_message_produced = value;
}
int error_message_produced(void)
next reply other threads:[~2008-06-17 14:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-17 14:14 wysochanski [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-02-08 11:31 LVM2 ./WHATS_NEW lib/log/log.c zkabelac
2011-10-22 16:52 zkabelac
2008-04-07 13:53 mbroz
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=20080617141401.17414.qmail@sourceware.org \
--to=wysochanski@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.