Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Git calls this "amend" and it is a feature of the regular 'git commit' tool. It doesn't do it based on commit message, you have to pass a '--amend' option to commit and it will combine the previous commit with the one you're creating. I haven't tried this with mercurial, but the <a href="http://mercurial.selenic.com/wiki/GitConcepts" rel="nofollow">GitConcepts page on the mercurial wiki</a> says you could run <code>hg rollback; hg commit -m "message"</code> to have the same affect.</p> <p>I should warn you that rollback will rollback the most recent commit in the repository (tip), so if you have pulled changes or merged things since your last regular commit, rollback will most likely not rollback the changeset you want it to. Additionally if you have pushed changes (or others have pulled from you) you will be breaking compatibility with those repositories because you're essentially editing history.</p> <p>In theory you could write a hook which will see if the tip of the repository is on the same branch that you're on and if its commit message matches the one you're entering, and if so do a rollback and a commit in one go.</p> <p>I'm curious to know what your goal is as that will help in recommending a solution for that goal. There may be better and more elegant ways to produce the result you desire than combining changesets. I know that you're not interested in extensions for some reason, but if you're trying to achieve a clean and logical changeset history, you should look in to the <a href="http://mercurial.selenic.com/wiki/MqExtension" rel="nofollow">MqExtension</a>.</p>
    singulars
    1. This table or related slice is empty.
    1. POMercurial - Automatically collapsing commits based on message?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USMark Drago
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POMercurial - Automatically collapsing commits based on message?
      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. COIt's not that I do not like the extensions... it's that they are a manual process. I do not see a way to have them automatically determine if the previous commit was for the same purpose and combine the changeset into a new "cleaner" version. Having the rollback + resubmit would work if I knew I was the last one to touch the repository, but that's not something I want to rely on. I don't foresee why editing the branch to combine changesets would be an issue if someone else branched a changeset to merge later. In fact, I assume it would make for faster merging.
      singulars
      1. PO
      1. USAndir
    2. COSo, I actually tried this with mercurial last night. I had some local changes that I wanted to amend to the previous commit. I ran 'hg rollback' and then 'hg commit' and it resulted in one commit without any errors. I think in theory you could get conflicts at rollback-time, but I didn't experience that.
      singulars
      1. PO
      1. USMark Drago
    3. COYep, it works if you know that the last commit is something you want to manually 'undo.' But it doesn't solve the problem of multiple small commits for the same purpose automatically. Just as I noted with the extensions, it's a manual process.
      singulars
      1. PO
      1. USAndir
 

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