StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20724594
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-12-21T23:23:43.370
FavoriteCount
0
LastActivityDate
2017-07-22T20:52:12.900
LastEditDate
2017-07-22T20:52:12.900
LastEditorUserId
1743225
OwnerUserId
1743225
ParentId
11694065
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I had the same problem today. The problem is probably that the SVN repository does not have a trunk directory. The standard trunk, tags and branches directories seems to be optional in SVN. But git-svn needs to know about this when migrating. It is also possible that some of the directories are there but named differently. (for example trunk could be named "project" instead of "trunk", branches could be named "branches" as usual and tags could be missing. Or "trunk" could be named "Trunk".) <ul> <li>If there are none of these standard directories in the SVN repo, and everything is just placed in the root of the repo, the solution is simply to not to try clone the standard svn-directories. Just clone the root.</li> <li>If they exists (or some of them does), but under different names, git-svn has to be told about these names.</li> </ul> I used Tortoise Git to migrate from SVN to GIT. In TortoiseGit, it is done by cloning from the svn repository (yep!) and checking the "From SVN Repository" checkbox. <ul> <li>If there are no trunk, tags or branches directories in the SVN repo, simply uncheck the "trunk", "tags" and "branches" checkboxes in the "From SVN Repository" section of the clone dialog.</li> <li>If the standard directories are there, but are named differently than normal, keep them checked but write the used names in the textbox next to them. (From the commandline this can be done with the -T, -t and -b switches. See <a href="http://www.sailmaker.co.uk/blog/2013/05/05/migrating-from-svn-to-git-preserving-branches-and-tags-3/" rel="nofollow noreferrer">http://www.sailmaker.co.uk/blog/2013/05/05/migrating-from-svn-to-git-preserving-branches-and-tags-3/</a> under "non-standard SVN layout").</li> </ul> (Those were the two cases i encountered - more complex cases may exist. I had several SVN repositories with neither trunk, tags or branches directories and unchecking these 3 checkboxes made it work. I also had a case where the trunk dir was called "project" instead of "trunk", but the branches dir was named normally and there were no tags dir. Unchecking the tags checkbox and entering the name of the trunk directory made that case work.)
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POgit-svn migration fatal: not a valid SHA1 update-ref refs/heads/master refs/remotes/trunk: command returned error: 128
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USBjarke
UserOwnerUserId
1. USBjarke
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. This table or related slice is empty.
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.