Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I have a bridge setup for some of my projects, but it's only one-way from git to svn (providing a public readonly SVN mirror of our git master branch). However, since it works fine it might help you or point you in the right direction in your two-way scenario anyway, as I assume it's git->svn that makes problems, not svn->git:</p> <p>My one-way scenario: Existing git repository at github, need a readonly svn mirror of the git master branch</p> <ul> <li><p>Create and initialize the target subversion repository on the Server:</p> <pre><code>svnadmin create svnrepo mkdir trunk svn import trunk svn://yoursvnserver/svnrepo rmdir -rf trunk </code></pre></li> <li><p>Create a mixed Git-Svn checkout and initialize subversion repository</p> <pre><code>git svn clone svn://yoursvnserver/svnrepo/trunk cd trunk git remote add github git://github.com/yourname/repo.git git fetch github git branch tmp $(cat .git/refs/remotes/github/master) git tag -a -m "Last fetch" last tmp INIT_COMMIT=$(git log tmp --pretty=format:%H | tail -1) git checkout $INIT_COMMIT . git commit -C $INIT_COMMIT git rebase master tmp git branch -M tmp master git svn dcommit --rmdir --find-copies-harder </code></pre></li> <li><p>Update the mirror</p> <pre><code>git fetch github git branch tmp $(cat .git/refs/remotes/github/master) git tag -a -m "Last fetch" newlast tmp git rebase --onto master last tmp git branch -M tmp master git svn dcommit --rmdir --find-copies-harder mv .git/refs/tags/newlast .git/refs/tags/last </code></pre></li> </ul> <p>This two articles from googlecode might help as well:</p> <ul> <li><a href="http://code.google.com/p/support/wiki/ImportingFromGit" rel="nofollow noreferrer">Importing from Git</a></li> <li><a href="http://code.google.com/p/support/wiki/ExportingToGit" rel="nofollow noreferrer">Exporting to Git</a></li> <li><a href="http://quirkygba.blogspot.com/2007/10/using-git-with-google-code-hosting.html" rel="nofollow noreferrer">Using Git with Google Code Hosting</a></li> <li><a href="http://google-opensource.blogspot.com/2008/05/develop-with-git-on-google-code-project.html" rel="nofollow noreferrer">Develop with Git on a Google Code Project</a></li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POgit clone of git-svn tree?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USFabian N.
    1. USChristoph Rüegg
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI have voted this answer up, since I think that it is generally useful, however it is based on a flawed premise. The problem is almost certainly not the git->svn, nor the svn->git, at least not directly. Rather the git-svn->git step will be the problem, since the history is being rewritten by the svn->git, which means that the two repositories will no longer have the same history, and life will become confusing.
      singulars
      1. PO
      1. USPaul Wagland
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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