public inbox for lvm2-cvs@sourceware.org
help / color / mirror / Atom feed
From: mbroz@sourceware.org
To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org
Subject: LVM2 ./WHATS_NEW doc/example_cmdlib.c
Date: Wed, 16 Jun 2010 13:03:00 -0000	[thread overview]
Message-ID: <20100616130352.29460.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	mbroz@sourceware.org	2010-06-16 13:03:51

Modified files:
	.              : WHATS_NEW 
	doc            : example_cmdlib.c 

Log message:
	Fix lvm2cmd example in documentation.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1612&r2=1.1613
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/doc/example_cmdlib.c.diff?cvsroot=lvm2&r1=1.2&r2=1.3

--- LVM2/WHATS_NEW	2010/06/16 13:01:25	1.1612
+++ LVM2/WHATS_NEW	2010/06/16 13:03:48	1.1613
@@ -1,5 +1,6 @@
 Version 2.02.68 -
 ===============================
+  Fix lvm2cmd example in documentation.
   Allow use of lvm2app and lvm2cmd headers in C++ mode.
   Fix wrong lvm path creation from configure introduced in previous release.
   Fix segfault in clvmd -R if no response from daemon received.
--- LVM2/doc/example_cmdlib.c	2009/07/15 23:57:55	1.2
+++ LVM2/doc/example_cmdlib.c	2010/06/16 13:03:50	1.3
@@ -13,10 +13,11 @@
  */
 
 #include "lvm2cmd.h"
+#include <stdio.h>
 
 /* All output gets passed to this function line-by-line */
-void test_log_fn(int level, int dm_errno, const char *file, int line,
-		 const char *format)
+void test_log_fn(int level, const char *file, int line,
+		 int dm_errno, const char *format)
 {
 	/* Extract and process output here rather than printing it */
 


                 reply	other threads:[~2010-06-16 13:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20100616130352.29460.qmail@sourceware.org \
    --to=mbroz@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).