Difference between revisions of "Git development"

From relax wiki
Jump to navigation Jump to search
(Transclusion of the {{historical svn}} template.)
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
{{historical svn}}
 +
__TOC__
 +
 
== Motivation ==
 
== 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  
 
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  
Line 25: Line 28:
  
 
Try commands in the browser, [http://try.github.io/levels/1/challenges/4 by clicking here.]
 
Try commands in the browser, [http://try.github.io/levels/1/challenges/4 by clicking here.]
 +
 +
Here is [http://git-scm.com/documentation the documentation.]
  
 
== Suggested faster development, keeping infrastructure ==
 
== Suggested faster development, keeping infrastructure ==
[[File:Git development.png|1200px|Suggested faster development, keeping infrastructure]]
+
[[File:Git development.png|1400px|Suggested faster development, keeping infrastructure]]
  
 
== See also ==
 
== See also ==
 
[[Category:Git]]
 
[[Category:Git]]

Latest revision as of 11:50, 27 October 2017

Caution  The information in this section is out of date but is kept for historical reasons. The relax source code is now hosted in a git rather than svn repository.

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

  1. make some lines of code
  2. make a path file and a commit message
  3. use the support tracker to upload patch and commit message
  4. wait for acceptance
  5. wait for commit to official repository
  6. then do an svn update
  7. 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.

Why git

See Linus Torvalds on git.

Try commands in the browser, by clicking here.

Here is the documentation.

Suggested faster development, keeping infrastructure

Suggested faster development, keeping infrastructure

See also