Difference between revisions of "Git asynchronous development"
Jump to navigation
Jump to search
| Line 20: | Line 20: | ||
=== Setup commit information === | === Setup commit information === | ||
If you havent set the repository variables for author information and commit message, this is good time. See [[Git_installation]]. | If you havent set the repository variables for author information and commit message, this is good time. See [[Git_installation]]. | ||
| + | |||
| + | == Example == | ||
| + | As an example, we can take the development of the NMRPipe SeriesTab reader: [https://gna.org/support/index.php?3043 sr #3043: Support for NMRPipe seriesTab format *.ser] | ||
| + | |||
| + | git add | ||
Revision as of 11:27, 24 June 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.
This can be solved by using git.
Initialization of git
Navigate to the root folder of the branch of relax, you want to develop. Initialize with:
git init
Setup commit information
If you havent set the repository variables for author information and commit message, this is good time. See Git_installation.
Example
As an example, we can take the development of the NMRPipe SeriesTab reader: sr #3043: Support for NMRPipe seriesTab format *.ser
git add
