Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There are three basic ways to do this depending on what you have done with the changes to the file A. If you have not yet added the changes to the index or committed them, then you just want to use the checkout command - this will change the state of the working copy to match the repository:</p> <pre><code>git checkout A </code></pre> <p>If you added it to the index already, use reset:</p> <pre><code>git reset A </code></pre> <p>If you had committed it, then you use the revert command:</p> <pre><code># the -n means, do not commit the revert yet git revert -n &lt;sha1&gt; # now make sure we are just going to commit the revert to A git reset B git commit </code></pre> <p>If on the other hand, you had committed it, but the commit involved rather a lot of files that you do not also want to revert, then the above method might involve a lot of "reset B" commands. In this case, you might like to use this method:</p> <pre><code># revert, but do not commit yet git revert -n &lt;sha1&gt; # clean all the changes from the index git reset # now just add A git add A git commit </code></pre> <p>Another method again, requires the use of the rebase -i command. This one can be useful if you have more than one commit to edit:</p> <pre><code># use rebase -i to cherry pick the commit you want to edit # specify the sha1 of the commit before the one you want to edit # you get an editor with a file and a bunch of lines starting with "pick" # change the one(s) you want to edit to "edit" and then save the file git rebase -i &lt;sha1&gt; # now you enter a loop, for each commit you set as "edit", you get to basically redo that commit from scratch # assume we just picked the one commit with the erroneous A commit git reset A git commit --amend # go back to the start of the loop git rebase --continue </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POGit undo changes in some files
      singulars
      1. PTQuestion
    1. PTAnswer
    1. US1800 INFORMATION
    1. US1800 INFORMATION
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POGit undo changes in some files
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. CONote: the revert does revert the all commit, so that could mean a lot of "reset B", isn't it ? See last comments of http://gitready.com/intermediate/2009/03/16/rolling-back-changes-with-revert.html . (as mentioned in http://stackoverflow.com/questions/642264/undo-change-in-git-not-rewriting-history/642809#642809 , a "negative merge" could be more accurate).
      singulars
      1. PO
      1. USVonC
    2. COYeah, if you had lots of files that were modified as part of the commit that you do not want to revert, then another method would be required, I'll edit it to suggest one
      singulars
      1. PO
      1. US1800 INFORMATION
    3. CO"git reset A" is equivalent to "git checkout HEAD A".
      singulars
      1. PO
      1. USJakub Narębski
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload