Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The default phase for a commit is <code>draft</code>, that's how they were treated when the phases didn't exist. When pushing a <code>draft</code> changeset, mercurial automatically changes its phase to <code>public</code>. You can use it to know which changesets you have already published or not.</p> <p>But the real issue is that when the changeset is in <code>public</code> phase, mercurial won't let you change them with history editing extensions (like <code>mq</code>, <code>rebase</code>, etc). That's really important, because the history editing happens <em>only</em> in the local repository, they don't propagate with <code>pull</code>/<code>push</code> operations. So, once a changeset is published, it's out of control, it's dangerous to change it.</p> <p>You can change from any phase to any other phase. The "normal flow" is to move to a higher phase (secret->draft->public), but Mercurial allows the change to a lower phase with the <code>--force</code> option. A phase change alone is harmless. For example, the only thing that happens when moving from <code>public</code> to <code>draft</code> or <code>secret</code> is that the protection of history editing is dropped, nothing else, pull and push will still work normally, Mercurial could never be confused about the changesets because they have unique identifiers. The history editing action that takes place <em>after</em> a phase change like this is what can cause problems. And that's why Mercurial gives the warning in the phase change and requires the <code>--force</code> option, as a confirmation that that's what you really want.</p> <p>In general published commits shoudn't be modified, that's what the phases try to ensure. But maybe you do have control over all repositories. Or maybe you pushed something and you know that no one else pulled it yet. Whatever is the reason, you have the option of forcing the phase of the changesets back to draft and edit them. But this edition must be done in every repository that has the changesets.</p>
    singulars
    1. This table or related slice is empty.
    1. POMercurial: what are the consequences of changing a phase?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRafael Piccolo
    1. USRafael Piccolo
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POMercurial: what are the consequences of changing a phase?
      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. COThanks for these details, however it doesn't answer my question: what happens when changing the phase of an existing changeset? E.g. from public to secret for a changeset which has already been pushed? Does that work or could it confuse Mercurial?
      singulars
      1. PO
      1. USmstrap
    2. COYou can change from any to any other phase. What happens is that if you try to change to a lower phase, you have to confirm it with `--force`. The phase change itself doesn't cause any problem. What can cause problem is what you do after changing the phase. When you change from `public` to `draft` you are removing a protection of history editing, it allows you to mess things up.
      singulars
      1. PO
      1. USRafael Piccolo
    3. COWhat about Mercurial -- could it get confused by changing from public to draft?
      singulars
      1. PO
      1. USmstrap
 

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