Difference between revisions of "Git Migration"
From OpenEMR Project Wiki
Bradymiller (talk | contribs) (Created page with 'On 10/30/2010, the official OpenEMR repository was moved from cvs to git on Sourceforge. The massive sourceforge thread that discussed this migration can be found here: http://s…') |
Bradymiller (talk | contribs) |
||
| Line 5: | Line 5: | ||
Plan to put more details on the migration, git settings, and mirroring mechanism here. | Plan to put more details on the migration, git settings, and mirroring mechanism here. | ||
Some Migration details: | |||
*PROBLEM: When compared the cvs and git repositories, all tags/branches were identical, except for the v3_1_0 tag and the rel-310 branch. | |||
*SOLUTION: Did not include the rel-310 branch in the migration. Will rebuild it after the migration. While rebuilding rel-310 will also add a v3_1_0_FIXED tag with appropriate code. So will require following steps: | |||
*:1. Create a rel-310 branch off the rel-320 branch in the git repo. | |||
:*2. Create a diff patch between rel-320 and v3_1_0 in cvs; use the cvs diff which can be used to ignore differences in EOL and not include cvs versioning lines. Apply this patch and commit to rel-310 branch, and then tag this with v3_1_0. | |||
:*3. Create a diff patch between rel-310 and v3_1_0 in cvs; use the cvs diff which can be used to ignore differences in EOL and not include cvs versioning lines. Apply this patch and commit to rel-310 branch. | |||
Revision as of 01:10, 1 November 2010
On 10/30/2010, the official OpenEMR repository was moved from cvs to git on Sourceforge.
The massive sourceforge thread that discussed this migration can be found here: http://sourceforge.net/projects/openemr/forums/forum/202506/topic/1412511
Plan to put more details on the migration, git settings, and mirroring mechanism here.
Some Migration details:
- PROBLEM: When compared the cvs and git repositories, all tags/branches were identical, except for the v3_1_0 tag and the rel-310 branch.
- SOLUTION: Did not include the rel-310 branch in the migration. Will rebuild it after the migration. While rebuilding rel-310 will also add a v3_1_0_FIXED tag with appropriate code. So will require following steps:
- 1. Create a rel-310 branch off the rel-320 branch in the git repo.
- 2. Create a diff patch between rel-320 and v3_1_0 in cvs; use the cvs diff which can be used to ignore differences in EOL and not include cvs versioning lines. Apply this patch and commit to rel-310 branch, and then tag this with v3_1_0.
- 3. Create a diff patch between rel-310 and v3_1_0 in cvs; use the cvs diff which can be used to ignore differences in EOL and not include cvs versioning lines. Apply this patch and commit to rel-310 branch.
