StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
164566
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2008-10-02T20:57:34.837
FavoriteCount
0
LastActivityDate
2017-06-20T09:51:51.310
LastEditDate
2017-06-20T09:51:51.310
LastEditorUserId
1000551
OwnerUserId
8912
ParentId
156280
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
After some digging, I came across the <a href="https://www.mercurial-scm.org/wiki/RdiffExtension" rel="nofollow noreferrer">Rdiff extension</a> that does most of what I want it to. It doesn't come with mercurial, but it can be installed by cloning the repository: <pre><code>hg clone http://hg.kublai.com/mercurial/extensions/rdiff </code></pre> And then modifing your ~/.hgrc file to load the extension: <pre><code>[extensions] rdiff=~/path/to/rdiff/repo/rdiff.py </code></pre> It's a little quirky in that it actually modifies the existing "hg diff" command by detecting if the first parameter is a remote URL. If it is then it will diff that file against your tip file in your local repo (not the working copy). This as the remote repo is first in the arguments, it's the reverse of what I'd expect, but you can pass "--reverse" to the hg diff command to switch that around. I could see these being potential enhancements to the extension, but for now, I can work around them with a bash/zsh shell function in my starup file. It does a temp checkin of my working copy (held by the mercurial transaction so it can be rolled back), executes the reverse diff, and then rolls the transaction back to return things back to the way they were: <pre><code>hgrdiff() { hg commit -m "temp commit for remote diff" && hg diff --reverse http://my_hardcoded_repo $* && hg rollback # revert the temporary commit } </code></pre> And then call it with: <pre><code>hgrdiff <filename to diff against remote repo tip> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUsing Mercurial, is there an easy way to diff my working copy with the tip file in the default remote repository
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USVadim Kotov
UserOwnerUserId
1. USTed Naleid
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POUsing Mercurial, is there an easy way to diff my working copy with the tip file in the default remote repository
 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
 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.