Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 4067386
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 20, 20262026-05-20T16:14:34+00:00 2026-05-20T16:14:34+00:00

When I have to commit merges I’ve done in mercurial, I just do hg

  • 0

When I have to commit merges I’ve done in mercurial, I just do hg commit -m "Merge."

What do you usually do when Merging? Do you write the changesets in a comment, or try to write “meaningfull” comments (since I think they are useless, except when you’re doing merges from two really different repos in different locations).

Is it possible to create an alias in mercurial (like hgmerge) in [alias] in hgrc, that automatically does hg commit -m "Merge: heads ${head}, ${head} ..."?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-20T16:14:35+00:00Added an answer on May 20, 2026 at 4:14 pm

    It would be easy to create that alias (I’ll do it below) but it’s also of almost no value. It’s very easy to pull the parent1 and parent2 values out of a merge changeset, so it’s not really telling you anything more than just “merge” would.

    Personally, even on single person repos I try to put something at least halfway useful even if it’s just something like these:

    • merging configuration work into code
    • merging work from desktop into work from laptop
    • merging away an anonymous branch I didn’t like
    • forgot to pull/update before editing

    There’s always some reason history diverged, even if it’s a totally mundane reason like forgetting to update or working disconnected at the coffeeshop, and that’s what I note.

    That said you could do this:

    hg commit -m "merging: $(hg parents --template '{node|short}\n') | xargs"
    

    which you sould make a shell alias with:

    [aliases]
    mycommit = !$HG hg commit -m "merging: $(hg parents --template '{node|short}\n') | xargs"
    

    Allowing you to run hg mycommit, but just dig for the better description.

    P.S. Someone is going to suggest the fetch extension. Ignore them.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have an application using Tomcat/Spring 3/JPA/Hibernate but my merges do not commit to
I have this setup where in my development copy I can commit changes on
I want to commit a large amount of XML files which have been modified.
Let's say I have committed some bad changes to Subversion repository. Then I commit
I am somewhat lost in merges. I develop in a single branch and merge
We've just recently switched over from SVN to Mercurial, but now we are running
We have several large subprojects inside our main SVN project root. I commit and
Say I have a feature branch, into which I merge upstream changes prior to
I have a trunk (A) and two branches (B and C). When I merge
I'm working on a project where I have a commit that introduced a feature

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.