[EMAIL PROTECTED] wrote:
Quoting Yan Langlois <[EMAIL PROTECTED]>:

Last year, I used Xindice1.1b4 in a project for my school (I am a student). Since then, I would like to contribute to Xindice. To begin, I would like to fix trivial bugs from Bugzilla in order to get a good understanding of source files.

Great.


I read a lot of messages from the mailing list but I did not understand how to commit:

* Can I commit a change like I checked Xindice's files out from CVS ?

No, you can't, not at the moment. Read more here: http://www.apache.org/foundation/how-it-works.html And, particularly, http://www.apache.org/foundation/how-it-works.html#roles


   * Or, Should I send the "cvs diff" output of the modified file to
     the mailing list and someone else will commit himself  the file ?

Yes, attach "diff -u" patched to the Bugzilla issues, and add a prefix [PATCH] to the bug summary.



If you do not have commit status, which is probably the case, you should
generate diff -u formatted patch files and add them to Bugzilla, i believe.

No, he does not. And yes, you are right. :)

Vadim

Reply via email to