Difference between revisions of "Git development"
Jump to navigation
Jump to search
(→How to) |
(→How to) |
||
| Line 13: | Line 13: | ||
== How to == | == How to == | ||
| + | How to setup your development Git branch, is explained here: [[Git_svn|Git svn]]. | ||
| − | + | To tweak Git setup, read here: [[Git_installation | Git installation]]. | |
An working example can bee seen here at: [[Git_asynchronous_development|Git asynchronous development]] | An working example can bee seen here at: [[Git_asynchronous_development|Git asynchronous development]] | ||
How to create SVN compatible pathches in Git, can be see here: [[Git_patch|Git patch]]. | How to create SVN compatible pathches in Git, can be see here: [[Git_patch|Git patch]]. | ||
| − | |||
| − | |||
== Suggested faster development, keeping infrastructure == | == Suggested faster development, keeping infrastructure == | ||
Revision as of 23:31, 23 July 2013
Motivation
Subversion needs an online repository, to store each commits. Subsequent calls to svn diff > patch will generate the difference according to the last revision. Therefore the development at the moment, require to
- make some lines of code
- make a path file and a commit message
- use the support tracker to upload patch and commit message
- wait for acceptance
- wait for commit to official repository
- then do an svn update
- then return to point 1
This takes time, and require that repository maintainer is online.
If the above scheme is not followed, the patch files will come out of sync.
How to
How to setup your development Git branch, is explained here: Git svn.
To tweak Git setup, read here: Git installation.
An working example can bee seen here at: Git asynchronous development
How to create SVN compatible pathches in Git, can be see here: Git patch.
Suggested faster development, keeping infrastructure
