[ https://issues.apache.org/jira/browse/CONNECTORS-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13171990#comment-13171990 ]
Karl Wright commented on CONNECTORS-314: ---------------------------------------- bq. Used GnuWin32 diff command bq. diff -rupN original modified > original.patch In general, when working with svn, it is better to have a single patch file produced with a single svn diff command, against a working directory that contains a checked-out version of the tree (from an appropriate branch or time), plus your changes. svn diff annotates the diff with revision numbers which makes it possible to apply the patch in a sensible way. So the usual procedure is: - check out the project - modify the checked out code through whatever means - do a "svn diff >XXX.patch" command to capture the changes Bear in mind that for added files you will need to do "svn add <filename>" in order for "svn diff" to pick it up later. But other than that it's a very straightforward process. Hope this helps. > Combined MySQL and i18n/Japanese contribution > --------------------------------------------- > > Key: CONNECTORS-314 > URL: https://issues.apache.org/jira/browse/CONNECTORS-314 > Project: ManifoldCF > Issue Type: Improvement > Components: Framework agents process, Framework core, Framework > crawler agent > Affects Versions: ManifoldCF 0.5 > Reporter: Karl Wright > Assignee: Karl Wright > Labels: I18N, mysql > Fix For: ManifoldCF 0.5 > > Attachments: connectors.patch, framework.patch > > > Hitoshi Ozawa wishes to contribute i18n support, a Japanese localization, and > MySQL database support, all in one patch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira