From: Kern Sibbald Date: Sat, 26 Nov 2011 11:09:59 +0000 (+0100) Subject: Fix error in developers pluginAPI chapter X-Git-Tag: Release-5.2.3~8 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=9044bfff1a29e54894e26de1e09a78ae1842ae23;p=bacula%2Fdocs Fix error in developers pluginAPI chapter --- diff --git a/docs/manuals/en/developers/pluginAPI.tex b/docs/manuals/en/developers/pluginAPI.tex index 42103f20..2a36b7a8 100644 --- a/docs/manuals/en/developers/pluginAPI.tex +++ b/docs/manuals/en/developers/pluginAPI.tex @@ -491,13 +491,13 @@ Most of the above are self-explanatory. \item [bEventVssBackupAddComponents] \item [bEventPluginCommand] is called for each PluginCommand present in the - current FileSet. The event will be sent only on plugin specifed in the - command. The argument is the PluginCommand (not valid after the call). + current FileSet. The event will be sent only on plugin specifed in the + command. The argument is the PluginCommand (not valid after the call). \item [bEventHandleBackupFile] is called for each file of a FileSet when - using a Options Plugin. If the plugin returns CF_OK, it will be used for the - backup, if it returns CF_SKIP, the file will be skipped. Anything else will - backup the file with Bacula core functions. + using a Options Plugin. If the plugin returns CF\_OK, it will be used + for the backup, if it returns CF\_SKIP, the file will be skipped. + Anything else will backup the file with Bacula core functions. \end{description} During each of the above calls, the plugin receives either no specific value or