Well you could:
1) zip up the files and use the patch on sourceforge
to upload your change. Then on of the devs with write
access can then upload your changes to CVS. To submit
a patch go to the followinf URL:
http://sourceforge.net/tracker/?group_id=5757&atid=305757
2) Sign-up with SourceForg
I don't mind just committing the code with CVS, it's easier than doing
the whole patch deal. As long as you don't mind me checking in the
stuff before someone looks it over. Do you prefer me using the patch
method or just commiting it with CVS?
I can always make a list of the changes I made.
CVS is the better of the two options. Please make sure
that you first have the lastest version in CVS before
merging your changes. As for documentation on change
please use the docs/docs/revision.html file
--
Raymond Irving
--- Jesse Vitrone <[EMAIL PROTECTED]> wrote:
OK, I merged with CVS the other day with no problems, I'll make sure I
do it again before committal.
My source forge user name is jessev.
Jesse
Raymond Irving wrote:
CVS is the better of the two options. Please make sure
that you first have the lastest version in CVS before
merging your change
One other question... Does the compressor checks for
missing semi-colons (;)? It would be very good if it
does and had the ability to insert the missing
semi-colon.
--
Raymond Irving
--- Jesse Vitrone <[EMAIL PROTECTED]> wrote:
> OK, I merged with CVS the other day with no
> problems, I'll mak
I'd love to add something like that, but does anyone know all the rules
for when to add? If we could come up with a good algorithm for that,
I'd be up for adding it to the code.
Jesse
Raymond Irving wrote:
One other question... Does the compressor checks for
missing semi-colons (;)? It w
