Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<blockquote> <p>Subversion is just like container to contain git</p> </blockquote> <p>Be sure to read the CAVEATS section coming with <strong><a href="http://git-scm.com/docs/git-svn#_caveats" rel="nofollow noreferrer">git-svn</a></strong>:</p> <h3>CAVEATS</h3> <blockquote> <p>For the sake of simplicity and interoperating with a less-capable system (SVN), it is recommended that all <code>git svn</code> users <code>clone</code>, <code>fetch</code> and <code>dcommit</code> directly from the SVN server, and avoid all git clone/pull/merge/push operations between git repositories and branches.<br> The recommended method of exchanging code between git branches and users is git <code>format-patch</code> and <code>git am</code>, or just 'dcommit’ing to the SVN repository.</p> <p><strong>Running <code>git merge</code> or <code>git pull</code> is NOT recommended on a branch you plan to <code>dcommit</code> from</strong>.<br> Subversion does not represent merges in any reasonable or useful fashion; so users using Subversion cannot see any merges you’ve made. Furthermore, if you merge or pull from a git branch that is a mirror of an SVN branch, <code>dcommit</code> may commit to the wrong branch.</p> </blockquote> <p>So you can adopt any merge and <a href="https://stackoverflow.com/questions/2563836/sell-me-distributed-revision-control/2563917#2563917">publication</a> workflow with Git, as long as you leave the SVN branches you mirror alone (in term of merges or rebases).</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload