StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POMercurial - Automatically collapsing commits based on message?
primarykey
Id
6102389
data
AcceptedAnswerId
6102825
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-05-23T20:05:26.297
FavoriteCount
1
LastActivityDate
2011-05-24T14:29:05.297
LastEditDate
2011-05-24T14:29:05.297
LastEditorUserId
257067
OwnerUserId
257067
ParentId
0
PostTypeId
1
Score
1
ViewCount
272
LastEditorDisplayName
text
Body
If I submit two or more commits into Mercurial with the same message, is there a way to collapse these into one change-set automatically? I assume this would have to be done in a changeset hook but I have not been able to find an automated method for this. Most examples require knowing the changeset revision numbers to collapse it manually and I'd want a way to automatically compare the previous change with the one being submitted and "merge" the two into one changeset. In other words: <pre><code>hg commit -m "some change" hg commit -m "some change" | * 20 <- "some change" | * 19 <- "some change" | * .. </code></pre> Could this automatically become one changeset and fold it with the last one with the same commit message? <pre><code>| * 19 <- "some change" | * .. </code></pre> This would only collapse changes if the commit message is exactly the same and sequential. Because I know someone will try to point to these again... I'm not looking for these extensions, but an automatic method that does not require knowing the IDs or revisions. <a href="http://mercurial.selenic.com/wiki/ConcatenatingChangesets" rel="nofollow">ConcatenatingChangesets</a> <a href="http://mercurial.selenic.com/wiki/CollapseExtension" rel="nofollow">CollapseExtension</a> <a href="http://mercurial.selenic.com/wiki/HisteditExtension" rel="nofollow">HisteditExtension</a> <hr> Would this be possible if I 'tag'ged the previous commit? Could you combine your next commit into a tagged commit?
Tags
<mercurial>
Title
Mercurial - Automatically collapsing commits based on message?
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USAndir
UserOwnerUserId
1. USAndir
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POMercurial - Automatically collapsing commits based on message?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POMercurial - Automatically collapsing commits based on message?
 UserUserId
 USPaolo
 VoteTypeVoteTypeId
 VTFavorite
CommentsPostId
1. This table or related slice is empty.

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.