StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
221137
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2008-10-21T08:18:18.783
FavoriteCount
0
LastActivityDate
2010-10-17T13:49:00.467
LastEditDate
2010-10-17T13:49:00.467
LastEditorUserId
9410
OwnerUserId
9410
ParentId
218023
PostTypeId
2
Score
45
ViewCount
0
LastEditorDisplayName
Aristotle Pagaltzis
text
Body
From the root directory of your working copy just do <pre><code>git checkout A2 -- . git commit -m 'going back to A2' </code></pre> <hr> Using <a href="http://www.kernel.org/pub/software/scm/git/docs/git-revert.html" rel="noreferrer"><code>git revert</code></a> for this purpose would be cumbersome, since you want to get rid of a whole series of commits and <code>revert</code> undoes them one at a time. You do not want <a href="http://www.kernel.org/pub/software/scm/git/docs/git-revert.html" rel="noreferrer"><code>git reset</code></a> either. That will merely change your <code>master</code> branch pointer: you are left with no record of the mistaken direction. It is also a pain to coordinate: since the commit you changed <code>master</code> to is not a child of the remote repository’s <code>master</code> branch pointer, pushing will fail – unless you add <code>-f</code> (force) or delete the <code>master</code> branch in the remote repository first and recreate it by pushing. But then everyone who tries to pull will still have the old history in their local <code>master</code> branch, so once <code>origin/master</code> diverges, <code>git pull</code> will try to perform a merge. This is not the end of the world: they can get out of this situation by doing <code>git rebase --onto origin/master $old_origin_master_commit master</code> (ie. rebase their local commits made on top of the old <code>origin/master</code> onto the top of the new <code>origin/master</code>). But Git will not know to do this automatically so you have to coordinate with every collaborator. In short, don’t do that.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORolling back in Git
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USAristotle Pagaltzis
UserOwnerUserId
1. USAristotle Pagaltzis
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.