[asterisk-commits] lmadsen: branch 1.6.2 r192097 - in /branches/1.6.2: ./ apps/app_forkcdr.c
SVN commits to the Asterisk project
asterisk-commits at lists.digium.com
Mon May 4 12:45:46 CDT 2009
Author: lmadsen
Date: Mon May 4 12:45:43 2009
New Revision: 192097
URL: http://svn.asterisk.org/svn-view/asterisk?view=rev&rev=192097
Log:
Merged revisions 192096 via svnmerge from
https://origsvn.digium.com/svn/asterisk/trunk
........
r192096 | lmadsen | 2009-05-04 13:42:56 -0400 (Mon, 04 May 2009) | 4 lines
Commit documentation changes related to issue #14801.
(issue #14801)
........
Modified:
branches/1.6.2/ (props changed)
branches/1.6.2/apps/app_forkcdr.c
Propchange: branches/1.6.2/
------------------------------------------------------------------------------
Binary property 'trunk-merged' - no diff available.
Modified: branches/1.6.2/apps/app_forkcdr.c
URL: http://svn.asterisk.org/svn-view/asterisk/branches/1.6.2/apps/app_forkcdr.c?view=diff&rev=192097&r1=192096&r2=192097
==============================================================================
--- branches/1.6.2/apps/app_forkcdr.c (original)
+++ branches/1.6.2/apps/app_forkcdr.c Mon May 4 12:45:43 2009
@@ -47,7 +47,7 @@
<optionlist>
<option name="a">
<para>Update the answer time on the NEW CDR just after it's been inited.
- The new CDR may have been answered already, the reset that forkcdr does
+ The new CDR may have been answered already. The reset that forkcdr does
will erase the answer time. This will bring it back, but the answer time
will be a copy of the fork/start time. It will only do this if the initial
cdr was indeed already answered.</para>
@@ -64,7 +64,8 @@
reset.</para>
</option>
<option name="e">
- <para>End the original CDR. Do this after all the necc. data.</para>
+ <para>End the original CDR. Do this after all the neccessry data is copied
+ from the original CDR to the new forked CDR.</para>
</option>
<option name="r">
<para>Do <emphasis>NOT</emphasis> reset the new cdr.</para>
More information about the asterisk-commits
mailing list