Hi Andre,
On Mon, Apr 26, 2010 at 1:51 PM, Andre Smit freev...@gmail.com wrote:
I'm confused, my natural state of mind :)
Mine too ;)
In the Developer Guide, Section "Contributing changes" you indicate:
- Send the patches like described in the previous Section.
This is unclear - the previous section (Making changes?) doesn't discuss patches. Also - why generate patches if the commits already reflect changes?
I guess Robert meant the "Without git" section, i.e., attach the patches to this mailing list or the issue tracker on google code. Probably it would be more clear IMHO to repeat this information on step 5.
For the second question, I guess generating patches are just one way. The other way would be to publish your git repository on, e.g., github. Then you can setup your local git copy to push your commits to github and then Robert can pull them into the main sfepy repository.
HTH! Keep asking questions! Also, feel free to edit and clarify and add to the documentation...it needs a lot of work yet. Btw, I really like your beginner's tutorial on the google wiki page. Perhaps we can incorporate it into the rst documentation?
Logan
-- You received this message because you are subscribed to the Google Groups "sfepy-devel" group. To post to this group, send email to sfepy...@googlegroups.com. To unsubscribe from this group, send email to sfepy-devel...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sfepy-devel?hl=en.