Joined: May 31, 2003 Posts: 219 Location: French Alps
Posted: Thu Feb 17, 2005 6:24 am Post subject: Commiting change to the CVS tree
In this thread, I suggested that a few missing declarations might prevent a user to use an optional dictionary.
This raise a question: Is it possible and desirable that we, testers-helpers, commit changes to the repository?
I have not enough resources (bandwith/disk space) to checkout and compile NeoJ locally. So its probably unsane I'd do it.
If I'd be able to test such minor modification would you, dev team, wish it?
I would suggest that you just submit a patch for a file that you think should be modified. You don't need to compile Neo/J. Instead, checkout the code, make your changes, invoke "cvs diff -u <file>" to create a patch, and attach the patch to a Bugzilla issue.
I or Ed can then rebuild our workspace with your patch and commit it if we think it is OK.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You cannot download files in this forum
