StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1295390
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-08-18T17:35:39.060
FavoriteCount
0
LastActivityDate
2009-08-18T17:35:39.060
LastEditDate
LastEditorUserId
0
OwnerUserId
158594
ParentId
1268279
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
Say your SVN repo is at svn+ssh://username@svn_server/svn/your_repo and your SVN repository has a "proper" layout (trunk, branches, tags) Here's workflow I've been using for few months now: 1. 'mkdir your_repo' 2. 'cd your_repo' 3. 'git svn clone -s svn+ssh://username@svn_server/svn/your_repo .' (mind the dot) 4. [wait a while depending on the size of your repository :)] now your GIT 'master' tracks the SVN trunk you can also make a tracking branch like you'd normally do with git if you're working on some branch 5. the traditional hack hack hack 6. update your clone with 'git svn fetch && git svn rebase' 7. "push" your changes to svn with 'git svn dcommit' More good stuff Define following handy aliases in your .gitconfig: 1. Alias 'spull' which stands for svn-pull like this: 'spull = !git svn fetch && git svn rebase' 2. Alias 'spush' which stands for svn-push like this: 'spush = !git svn dcommit' These aliases turn the workflow in to pure effectiveness: clone/hack hack/spull/spush -> profit svn:externals I couldn't find a good solution for this in the internet, so made one myself :) <a href="http://github.com/sushdm/git_svn_externals/tree/master" rel="nofollow noreferrer">http://github.com/sushdm/git_svn_externals</a> it's not yet perfect, but it should definetely make life a lot easier. Works for me perfectly well, hope it helps you.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUse local Git repository with a master Subversion repository
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USDmitry
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
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
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.