usage: {0} [-hiv] [-o comment] [-p command] [files ...]
 
help:\
NAME\n\
\    {0} - convert diffs from Perforce to patch format\n\
\n\
SYNOPSIS\n\
\    {usage}\n\
\n\
\    Options:\n\
\      -h          Display this help message\n\
\      -i[suffix]  Edit files 'in place'; add suffix to the original file name\n\
\      -o comment  Output the comment instead of the old file version\n\
\      -p command  Use the command instead of `p4 print -q` to get files\n\
\      -v          Output progress messages\n\
\n\
DESCRIPTION\n\
\    Change diffs in Perforce format (from `p4 diff`, `p4 diff2` or `p4\n\
\    describe`) to a form suitable for input to the GNU `patch` program.\n\
\    Insert headers and diffs, but don''t remove anything.\n\
\n\
\    Edit each file in place if file names are given; otherwise filter from\n\
\    input to output.\n\
\n\
EXAMPLES\n\
\    p4 diff -du ...@ver8_0 | {0} -o \"-r v80\" | patch -p3\n\
\    p4 diff2 -dc ...@Beta1 ...@Beta2 | {0} -o \"-r Beta1\" | patch -p5\n\
\    p4 describe -du 123 | {0} -o \"@122\" | patch -p2\n\
\n\
KNOWN BUGS\n\
\    RCS format diffs (from `p4 diff -dn`) are not converted.\n\
\n\
SEE ALSO\n\
\    To generate a patch from a change number:\n\
\    http://public.activestate.com/gsar/APC/perl-current/Porting/p4genpatch\n\
\n\
\    To generate a patch for added files:\n\
\    http://public.activestate.com/gsar/APC/perl-5.6.x/Porting/p4desc\n\
\n\
\    Perforce http://www.perforce.com/perforce/technical.html\n\
\n\
\    GNU `patch`\n\
\    http://www.gnu.org/software/diffutils/manual/html_node/Multiple-Patches.html\n\
\n\
AUTHOR\n\
\    John Kristian <jk2005@engineer.com>.  Thanks to Gurusamy Sarathy for\n\
\    inspiration; but I accept all blame.\n\
 
diff.default: converting default diff (not recommended for `patch`)\n