Permalink
Browse files

Starting to publish misc textual project info.

  • Loading branch information...
0 parents commit 18283143def0efd133732a5a4efbe54c76607ab9 @divanorama committed Jun 5, 2011
Showing with 183 additions and 0 deletions.
  1. +1 −0 .gitignore
  2. +21 −0 _layouts/default.html
  3. +38 −0 forest.html
  4. +6 −0 index.html
  5. +68 −0 proposal.html
  6. +49 −0 references.html
@@ -0,0 +1 @@
+/_site
@@ -0,0 +1,21 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en-us">
+<head>
+ <meta http-equiv="content-type" content="text/html; charset=utf-8" />
+ <title>GSoC'11 {{ page.title }}</title>
+</head>
+<body>
+ <h1> {{ page.title }} </h1>
+
+ {{ content }}
+
+ <hr/>
+ <ul>
+ <li><a href="/index.html">Home</a></li>
+ <li><a href="/proposal.html">Initial proposal</a></li>
+ <li><a href="/references.html">References</a></li>
+ <li><a href="/forest.html">Forest</a></li>
+ </ul>
+ <p><a href="https://github.com/divanorama/gsoc11/blob/gh-pages{{ page.url }}">This page on github</a></p>
+</body>
+</html>
@@ -0,0 +1,38 @@
+---
+layout: default
+title: Forest
+---
+<h3>git://github.com/divanorama/git.git</h3>
+<p>The main tree to publish the project work.
+And is the only one of mentioned here owned by me.</p>
+
+<h3>git://repo.or.cz/git/jrn.git svn-fe-{maint,next,pu}</h3>
+<p>A patch queue for svn-fe is maintained here.</p>
+
+<h3>git://github.com/artagnon/git.git svn-fi</h3>
+<p>This is the home for svn-fi work.</p>
+
+<h3>git://github.com/SRabbelier/git.git</h3>
+<p>Here you can find git-remote-hg.</p>
+
+<h3>git://github.com/SRabbelier/hg-git.git</h3>
+<p>Here you can find hg-git.</p>
+
+<h3>git://github.com/lelutin/git-remote-bzr.git</h3>
+<p>Here you can find git-remote-bzr.</p>
+
+<h3>git://github.com/Bibzball/Git-Mediawiki.git</h3>
+<p>Here you can find young git-remote-mediawiki.</p>
+
+<h3>git://github.com/wereHamster/git.git</h3>
+<p>Here you can find an experimental git remote svn helper for by Tomas Carnecky.</p>
+<p>It uses the new git fast-import-helper.
+It only works with local svn repos (not over network).
+It uses notes to save the git commit -&gt; svn revision mapping.</p>
+
+<h3>git://github.com/jherland/git.git</h3>
+<p>Here you can find a git-remote-cvs.</p>
+
+<h3>git://github.com/artagnon/svn-dump-fast-export.git</h3>
+<p>Here you can find svn-dump-fast-export.</p>
+
@@ -0,0 +1,6 @@
+---
+layout: default
+title: git-remote-svn
+---
+<p>These pages are set up by GSoC'11 student Dmitry Ivankov to track
+various textual information of the project.</p>
@@ -0,0 +1,68 @@
+---
+layout: default
+title: GSoC project proposal
+---
+<h3>Short description:</h3>
+<p>Complete the work on git-remote-svn, (re)implement git-svn on top of it.</p>
+<h4>Major motivation is:</h4>
+<ul>
+<li>git-svn git repository is not cloned easily, with git-remote-svn it could be much more straightforward.</li>
+<li>git-svn fetch is slow on huge repositories, especially when there are many branches.</li>
+</ul>
+
+<h3>Project goals:</h3>
+<ul>
+<li>Complete git-remote-svn and get it merged.</li>
+<li>Implement the foundation for new git-svn (git-svn-ng) and get it merged too.</li>
+</ul>
+
+<h3>Milestones for functionality:</h3>
+<ul>
+<li>
+Be able to track whole / as the only remote branch.
+Use svnrdump stream for a fast fetch.
+Commits will include actual diffs, and some of the metadata
+like svn:author, svn:date translated to git counterparts
+(what should be translated and what not needs some thinking, maybe it'll even be configurable).
+Commit history is linear with mutable (by svn upstream, maybe svn:log) and
+svn specific data (rev mapping, revprops) stored separately in git-notes.
+This should be made easy to git clone and proceed with tracking in two git repos,
+and of course not only clone but fetch furter svn updates from a git peer.
+</li>
+<li>
+Be able to commit fastforward linear changes to svn, via svnrdump for better speed.
+And be able to dcommit (rebase-push) changes.
+At this point it is already possible to try out git-svn-ng for normal work.
+</li>
+<li>
+Be able to track /svnroot/proj path in svn repo in just the same manner as in previous step.
+Hopefully svn layer understands paths already making this a quick step.
+</li>
+<li>
+Be able to track paths within svnroot as branches.
+The main difference from svnroot branch is how do we choose parents
+(this time whole history could be a tree, not only linear).
+svn cp on path is creating a branch / setting a parent.
+Set of branches to track is either a fixed list of fixed paths,
+or a list of floating path@rev (like trunk@1).
+In the latter case each time a path in 'svn cp'-ed
+we add destination@rev as one more floating path, if it is within svnroot of course.
+</li>
+</ul>
+
+<h3>Future development, not included in the minimalistic plan:</h3>
+<ul>
+<li>
+Find a way to push and fetch merges to svn.
+svn:mergeinfo could be a good place to store merge parents.
+</li>
+<li>
+Allow path or even revision filters to discard part of svn history.
+Like binaries directory, or a weird svn cp like /trunk -&gt; /trunk/some/path/.
+</li>
+<li>
+Investigate a possiblity to tweak the svn-git mapping and a push process
+such that any (reasonable for svn users) git history can be pushed to svn
+and then fetched back lossless, with the same sha1.
+</li>
+</ul>
@@ -0,0 +1,49 @@
+---
+layout: default
+title: References
+---
+<p>Here I will collect links to new public discussions as well as
+historic ones, links to related documentation and so on.</p>
+
+<p>GSoC project public proposal: <a href="http://thread.gmane.org/gmane.comp.version-control.git/171102">
+http://thread.gmane.org/gmane.comp.version-control.git/171102
+</a></p>
+
+<p>svn-fe history:</p>
+<ul>
+ <li>announcement and following thread:
+ <a href="http://thread.gmane.org/gmane.comp.version-control.git/143180/focus=143388">
+ http://thread.gmane.org/gmane.comp.version-control.git/143180/focus=143388</a>
+ <a href="http://thread.gmane.org/gmane.comp.version-control.git/143187">
+ http://thread.gmane.org/gmane.comp.version-control.git/143187</a>
+ </li>
+
+ <li>first public review:
+ <a href="http://thread.gmane.org/gmane.comp.version-control.git/147587">
+ http://thread.gmane.org/gmane.comp.version-control.git/147587</a>
+ </li>
+
+ <li>second review:
+ <a href="http://thread.gmane.org/gmane.comp.version-control.git/148409">
+ http://thread.gmane.org/gmane.comp.version-control.git/148409
+ </a>
+ </li>
+
+ <li>third review:
+ <a href="http://thread.gmane.org/gmane.comp.version-control.git/148866/focus=149097">
+ http://thread.gmane.org/gmane.comp.version-control.git/148866/focus=149097
+ </a>
+ </li>
+
+ <li>fourth review:
+ <a href="http://thread.gmane.org/gmane.comp.version-control.git/149571/focus=149934">
+ http://thread.gmane.org/gmane.comp.version-control.git/149571/focus=149934
+ </a>
+ </li>
+
+ <li>fifth review:
+ <a href="http://thread.gmane.org/gmane.comp.version-control.git/151086/focus=151144">
+ http://thread.gmane.org/gmane.comp.version-control.git/151086/focus=151144
+ </a>
+ </li>
+</ul>

0 comments on commit 1828314

Please sign in to comment.