Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Not exactly.</p> <p><code>hg pull</code> grabs the revisions from the other repository and adds them to the locally available revisions in your clone of the repository, but <em>does not update your working copy</em> - only your <em>repository</em> (which, for DCVS like hg/git/etc is not the same thing as a working copy).</p> <p><code>hg update</code> updates your actual working copy to the latest revision in your local repository.</p> <p>This differs from Subversion because in svn, there is no such thing as your "local repository" - the only repository is the one on the server; you only have a working copy locally. Hence why <code>update</code> is only a single command, as opposed to Mercurial's <code>pull</code> and then <code>update</code>.</p> <p>The equivalent to <code>svn update</code> for Mercurial would be <code>hg pull --update</code>, which is equivalent to doing <code>hg pull</code> and then <code>hg update</code> one after another.</p> <p>An end-to-end workflow for DCVS with a "central" repo looks something like this:</p> <ol> <li>A does <code>hg commit</code> on some changes.</li> <li>A does <code>hg push</code> to push them the central repository.</li> <li>B does <code>hg pull</code> to pull them from the central repository into their own clone.</li> <li>B does <code>hg update</code> to update their working copy to reflect the changes pulled into their clone.</li> </ol> <p>In systems without a central repo, it would instead look something like this:</p> <ol> <li>A does <code>hg commit</code> on some changes.</li> <li>B, who has cloned A's repo, wants those changes, and thus does an <code>hg pull</code> directly from A's repo.</li> <li>B uses <code>hg update</code> to update their working copy to the changes.</li> </ol> <p>Also, the equivalent to <code>svn revert</code> is <code>hg revert</code>. :)</p>
    singulars
    1. This table or related slice is empty.
    1. POIs `hg pull --rebase` analogous to `svn update`?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAmber
    1. USAmber
    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. COI know hg pull --rebase is equivalent to hg pull followed by hg rebase. What does rebase do? Will hg pull --update work if I have made commits to a branch that has commits that the hg pull is pulling down? Seems like that's what rebase is for, which is why I think of hg pull --rebase as being analogous to svn update: it takes changes from a central repo, merges them in to my working copy, and changes the parent of my working copy (conflicts may need to be resolved prior to commit).
      singulars
      1. PO
      1. USallyourcode
    2. CO`rebase` does a little more than just that - it actually reworks the commit history to move your "private" commits that happened before you pulled to be after any "public" commits that were newly pulled in. Thus, instead of having to commit a "merged" changeset, your local repo will appear to have already had all of the newly pulled changesets before you ever made your own private commits (hence the name "rebase" - you change what you were basing your private commits on).
      singulars
      1. PO
      1. USAmber
    3. COA graphical representation of what I'm talking about can be seen at http://mercurial.selenic.com/wiki/RebaseProject under the "A common case" heading.
      singulars
      1. PO
      1. USAmber
 

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