Hi, the commit below is a result of my modification of the bug.mdtext file on the CMS.
Rather than this notification, I’d much rather have the diff against the original Markdown source. Before I escalate this to infra@, does anyone know what can be done about it? Thanks, Vincent On 20/11/12 18:11, [email protected] wrote: > Author: buildbot > Date: Tue Nov 20 18:11:14 2012 > New Revision: 838953 > > Log: > Staging update by buildbot for xmlgraphics > > Modified: > websites/staging/xmlgraphics/trunk/content/ (props changed) > websites/staging/xmlgraphics/trunk/content/fop/bugs.html > > Propchange: websites/staging/xmlgraphics/trunk/content/ > ------------------------------------------------------------------------------ > --- cms:source-revision (original) > +++ cms:source-revision Tue Nov 20 18:11:14 2012 > @@ -1 +1 @@ > -1409086 > +1411775 > > Modified: websites/staging/xmlgraphics/trunk/content/fop/bugs.html > ============================================================================== > --- websites/staging/xmlgraphics/trunk/content/fop/bugs.html (original) > +++ websites/staging/xmlgraphics/trunk/content/fop/bugs.html Tue Nov 20 > 18:11:14 2012 > @@ -363,7 +363,15 @@ $(document).ready(function () { > <p>Review the <a > href="http://issues.apache.org/bugzilla/page.cgi?id=bug-writing.html";>Apache > Bug Writing Guidelines</a> before submitting your report.</p> > </li> > <li> > -<p>Enter a new issue report at <a > href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Fop";>The FOP > issue database (Bugzilla)</a> . You will be asked to login to an existing > Bugzilla account or to create a new one. When entering the bug report, please > make your description complete and concise. If appropriate, attach a minimal > fo file to your report which demonstrates the problem.</p> > +<p>Enter a new issue report at <a > href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Fop";>The FOP > issue database (Bugzilla)</a> . You will be asked to login to an existing > Bugzilla account or to create a new one. When entering the bug report, please > make your description complete and concise. If the issue involves a specific > input or output file, then please include the following information in the > bug report (preferably as one or more attachments):</p> > +</li> > +<li>an input XSL-FO file (if you generate the XSL-FO file from an input XML > using XSLT, then please directly provide the result of the transformation > (the XSL-FO output), not the XML input and XSLT). Please try and make the > XSL-FO input as small as possible; Ideally it would contain nothing more than > the minimum needed to demonstrate the problem. By doing this you increase > your chance that a developer will take the time to look at your file.</li> > +<li>a resulting output file, preferably in PDF format, unless the issue > being reported involves a different output format; In which case please > provide the output in that format;</li> > +<li>a copy of the FOP configuration file you used (e.g., fop.xconf), if > applicable;</li> > +<li>if FOP was invoked using the command line (or an equivalent), then a > dump of both the input command line and any console output (stderr or stdout) > produced; if the report involves an exception, be sure to include the full > stack trace;</li> > +<li>information describing the version of FOP you are using and the platform > (and OS) on which you are invoking FOP;</li> > +<li> > +<p>if the report applies to the use of a specific font other than one of the > built-in, base 14 fonts, then information that describes where to obtain the > font. If the font is not freely available, please describe your problem on > the <a href="maillist.html#fop-user" title="FOP users mailing > list">fop-users</a> mailing list, where a developer may step up and ask you > to send them the font privately for investigation purpose.</p> > </li> > <li> > <p>After submission, a copy of your bug report will be automatically sent to > the FOP developer discussion list.</p> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
