Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Here's the cheat sheet on the commands:</p> <ul> <li><p><strong><code>hg update</code></strong> changes your working copy parent revision and also changes the file content to match this new parent revision. This means that new commits will carry on from the revision you update to.</p></li> <li><p><strong><code>hg revert</code></strong> changes the file content only and leaves the working copy parent revision alone. You typically use <code>hg revert</code> when you decide that you don't want to keep the uncommited changes you've made to a file in your working copy.</p></li> <li><p><strong><code>hg branch</code></strong> starts a new named branch. Think of a named branch as a label you assign to the changesets. So if you do <code>hg branch red</code>, then the following changesets will be marked as belonging on the "red" branch. This can be a nice way to organize changesets, especially when different people work on different branches and you later want to see where a changeset originated from. But you don't want to use it in your situation.</p></li> </ul> <p>If you use <code>hg update --rev 38</code>, then changesets 39–45 will be left as a dead end — a dangling head as we call it. You'll get a warning when you push since you will be creating "multiple heads" in the repository you push to. The warning is there since it's kind of impolite to leave such heads around since they suggest that someone needs to do a merge. But in your case you can just go ahead and <code>hg push --force</code> since you really do want to leave it hanging.</p> <p>If you have not yet pushed revision 39-45 somewhere else, then you can keep them private. It's very simple: with <code>hg clone --rev 38 foo foo-38</code> you will get a new local clone that only contains up to revision 38. You can continue working in <code>foo-38</code> and push the new (good) changesets you create. You'll still have the old (bad) revisions in your <code>foo</code> clone. (You are free to rename the clones however you want, e.g., <code>foo</code> to <code>foo-bad</code> and <code>foo-38</code> to <code>foo</code>.)</p> <p>Finally, you can also use <code>hg revert --all --rev 38</code> and then commit. This will create a revision 46 which looks identical to revision 38. You'll then continue working from revision 46. This wont create a fork in the history in the same explicit way as <code>hg update</code> did, but on the other hand you wont get complains about having multiple heads. I would use <code>hg revert</code> if I were collaborating with others who have already made their own work based on revision 45. Otherwise, <code>hg update</code> is more explicit.</p>
    singulars
    1. This table or related slice is empty.
    1. POMercurial — revert back to old version and continue from there
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMartin Geisler
    1. USMartin Geisler
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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. VTUpMod
    1. COAWESOME answer. I used hg revert --all --rev ## and it saved my ass :D
      singulars
      1. PO
      1. USVan Thoai Nguyen
    2. COAnd hg clone --rev 38 foo foo-38 just saved mine. Thanks!!!
      singulars
      1. PO
      1. USNathan Hartley
    3. CO+1 for hg revert --all --rev X WOW. Beautiful.
      singulars
      1. PO
      1. USAdam Rackis
 

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