StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20201689
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-11-25T19:35:51.267
FavoriteCount
0
LastActivityDate
2013-11-25T19:35:51.267
LastEditDate
LastEditorUserId
0
OwnerUserId
899092
ParentId
20193003
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
This is what did the trick for me: <ol> <li>Create a svn repository dump file for later processing: <code>svnadmin dump /svn/old_repo > /tmp/svn/repository.dump</code></li> <li>Use <code>svndumpfilter</code> to split dump file into separate dumps: <code>svndumpfilter include /trunk/scr/folder1 --drop-empty-revs --renumber-revs --preserve-revprops < /tmp/svn/repository.dump > /tmp/svn/dump/folder1.dump</code></li> <li>Create new empty svn repository <code>svnadmin create /tmp/svn/repos/folder1</code></li> <li>Create root dir insde new empty svn repository. This is very important! I missed that step and almost gone mad due to some unclear svnadmin erros: <code>svn mkdir file:///tmp/svn/repos/folder1/trunk/src/folder1 --parents -m "Go"</code></li> <li>Load new dump into empty svn repository: <code>svnadmin load /tmp/svn/repos/folder1 < /tmp/svn/dump/folder1.dump</code></li> <li>Now some git magic. Note the <code>-T</code> arg - it's very handy. I used this to make my life easier and make <code>folder1</code> a root for git repo. If I didn't do that, I'd end up with a git repo structure like this: <code>trunk/src/folder1/*</code> (that is what I had initially in my svn repo). And I wanted to just have the <code>folder1</code> as a root: <code>git svn clone -T /trunk/src/folder1 file:///tmp/svn/repos/folder1 /new/path/folder1</code></li> </ol> And that was it. Steps 2-7 repeat for each directory for which you want to have a new git repository. I ended up writing a simple script for that.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POgit clone svn to split folders into separate git repositories
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USSiliconMind
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POgit clone svn to split folders into separate git repositories
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

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.