StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12973205
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-10-19T11:23:06.220
FavoriteCount
0
LastActivityDate
2012-10-19T11:23:06.220
LastEditDate
LastEditorUserId
0
OwnerUserId
1665124
ParentId
12910474
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
After having this problem with Egit I went back to using GitBash to try to create, push and pull repositories. I was then given this error: Git Bash error: <pre><code>fatal: http://xx.xx.x.xxx/mjtest.git/info/refs not found: did you run git update-server-info on the server? </code></pre> Egit error: <pre><code>Transport Error Cannot List the available branches Reason: Exception caught during execution of ls-remote command </code></pre> I found that the solution to both the GitBash and the Egit error was to create an empty file called <code>git-daemon-export-ok</code>and place it directly into the <code>xxxx.git</code> root directory of the repository on the server. The solution explained: I set up a repository in gitstack called <code>mjtest</code> and create myself a new username and password and add myself to the repository with read and write access. This is what I then do in GitBash: I set up my local repo: <pre><code>git config --global user.name "XXXXXXXX" git config --global user.email XXXXXXXX mkdir ~/mjtest cd ~/mjtest git init touch README </code></pre> Then I create the empty file: <pre><code>touch git-daemon-export-ok </code></pre> So now we have a local repository that has a file called <code>README</code> and our <code>git-daemon-export-ok</code>file in it. We now need to copy the <code>git-daemon-export-ok</code>file and place it directly into the <code>mjtest.git</code> folder in the server. Once that is done the <code>git-daemon-export-ok</code> file can be deleted from the local repository, as it just needs to be on the server. Adding, Commiting and Pushing: <pre><code>git add README git commit -m 'first commit' git remote add origin http://XX.XX.X.XXX/mjtest.git git push origin master </code></pre> This should work and you should be able to go onto your gitstack server and see your first commit. I then went back onto Egit and cloned the <code>http://XX.XX.X.XXX/mjtest.git</code> repository and it worked. Now both push and pull work in GitBash and Egit!
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POTransport error with Egit
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMikeyJ
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POTransport error with Egit
 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.