Changes between Version 7 and Version 8 of GitTransition

Timestamp:

03/30/10 16:05:44 (12 years ago)

Author:

kthakore

Comment:

--

GitTransition

@@ -4 +4 @@
  * Backwards-compatibility of svn revision numbers.  We aren't patient enough to change all references in Parrot and Trac to svn revisions, so there has to be a way to figure out what changes a svn revision refers to.  This can be done by maintaining a read-only version of the svn repository.
 
-** This is fixed by using "git svn clone" it keeps all rXXXX numbers in the commit messages
-** This can be linked to old links of rXXXX throughout trac (an experiment/trial will be needed)
+   * This is fixed by using "git svn clone" it keeps all rXXXX numbers in the commit messages
+   * This can be linked to old links of rXXXX throughout trac (an experiment/trial will be needed)
 
-  * When importing a SVN repo into Git, we have the choice of adding markers to each commit which reference the original SVN revision. It sounds like we want this.
+ * When importing a SVN repo into Git, we have the choice of adding markers to each commit which reference the original SVN revision. It sounds like we want this.
 
-** again git svn clone 
+   * again git svn clone 
 
  * Trac integration - We aren't switching away from Trac, so we need to be sure that there's a *mature* Trac plugin that can work with Git, either directly or via a third-party host like [http://github.com/davglass/github-trac GitHub].  This needs to be researched carefully since poor or immature Trac integration could be a significant impediment to Parrot's progress.
 
-** Trac has a git plugin (http://trac-hacks.org/wiki/GitPlugin)
-** Working example http://sdlperl.ath.cx/
+   * Trac has a git plugin (http://trac-hacks.org/wiki/GitPlugin)
+   * Working example http://sdlperl.ath.cx/
 
 == Things To Think About ==