RE: xalan-dev list proto-FAQ v0.3 - Readme First! -- Question abo ut the FAQ

[Patrick Moore <pa...@rioport.com>]

I have had various people suggest that I put the bug in bugzilla and then
attach the fixes there. That should probably be mentioned as the correcxt
procedure for bug fixes in the faq..

-Patrick Moore-

> 
> Q: How do I submit a patch to Xalan?
> A: Make your subject line start with [PATCH] and then note 
> the filename(s)
> and briefly what the patch does.
> In the body of the email, describe what you patched and why, and any
> questions or hints you might have for committers who will be 
> reviewing the
> patch.  Always include the patch as an attachment to the email: this
> prevents problems with mailers that wrap long lines.  If the patch is
> small, then *also* include a copy of the patch in the body of 
> the email
> itself (which makes it quicker to review).
> The best way to create a patch currently (someone suggest 
> better ways as
> needed) is to use the CVS diff command like so:
>   cvs diff -u FileName.java >> FileName.java.patch
> This creates a _u_nified diff of your local FileName.java 
> against the most
> recent revision in the repository, putting the output into
> FileName.java.patch
> For hints on using CVS, see http://xml.apache.org/cvs.html
> 

Re: xalan-dev list proto-FAQ v0.3 - Readme First! -- Question about the FAQ

[James Melton <ja...@cylogix.com>]

This is very helpful information. Is this in fact the "approved" way for
non-committers to submit code?

Jim.

Patrick Moore wrote:
> 
> I have had various people suggest that I put the bug in bugzilla and then
> attach the fixes there. That should probably be mentioned as the correcxt
> procedure for bug fixes in the faq..
> 
> -Patrick Moore-
> 
____________________________________________________________
James Melton                 CyLogix
609.750.5190                 609.750.5100
james.melton@cylogix.com     www.cylogix.com