StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4574375
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
19
CommunityOwnedDate
CreationDate
2011-01-01T14:38:14.307
FavoriteCount
0
LastActivityDate
2011-01-02T15:13:15.367
LastEditDate
2017-05-23T10:30:23.117
LastEditorUserId
-1
OwnerUserId
6309
ParentId
4574259
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
The ideal solution consiste to keep local Mercurial repo, and work only with this local repo to the existing bitbucket Mercurial remote repo. With a plugin <a href="http://hg-git.github.com/" rel="nofollow noreferrer">like Hg-Git</a>, you can at least push to and pull from a Git server repository from Mercurial, allowing you to pull from the GitHub repo to your local Mercurial repo. <img src="https://i.stack.imgur.com/BOsBY.png" alt="alt text"> From that local (Mercurial) repo, you can then work as usual with the bitbucket remote repo. <hr> The OP adds: <blockquote> It didn't work for me so i tried to transfer git repo to hg repo and from this repo pull to my working repo with changes - but it says that: abort: repository is unrelated - but I merged a lot from it. Any help here? </blockquote> That makes senses, if both repos have been developed separately, you cannot push/pull 2 (mercurial) repos one into another. This is confirmed at the bottom of the page "<a href="http://mercurial.selenic.com/wiki/UnderstandingMercurial#What_Mercurial_can.27t_do" rel="nofollow noreferrer">Understanding Mercurial</a>", and detailed in the blog post: "<a href="http://kevin-berridge.blogspot.com/2009/05/what-mercurial-cant-do-subtree-repos.html" rel="nofollow noreferrer">What Mercurial Can't Do: Subtree Repos</a>". The more practical solution would be to make one extra repository (a "parent one") with your two repos declared in it as <a href="http://mercurial.selenic.com/wiki/Subrepository?action=show&redirect=subrepos" rel="nofollow noreferrer">nested repository</a>. It would keep both repos independent, allowing to push back to the GitHub repo from your second mercurial repo. If you don't have to push back to GitHub, but really want to have one repo in which you merge common files, then you can look in "<a href="https://stackoverflow.com/questions/1368080/merge-tip-from-an-unrelated-repository-with-mercurial">Merge tip from an unrelated repository with Mercurial</a>", but that is much more complex. I would rather: <ul> <li>keep both repos separate</li> <li>delete from the first one the common files you need to merge in the second one.</li> <li>report and merge those common files in the second one.</li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POFrom github to bitbucket
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USVonC
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POFrom github to bitbucket
 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
 VTAcceptedByOriginator
CommentsPostId

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.