[Bug 4137] New: Patch to be committed as part of commit message help text

mercurial-bugs at selenic.com mercurial-bugs at selenic.com
Sun Dec 22 11:54:23 CST 2013


http://bz.selenic.com/show_bug.cgi?id=4137

          Priority: normal
            Bug ID: 4137
                CC: mercurial-devel at selenic.com
          Assignee: bugzilla at selenic.com
           Summary: Patch to be committed as part of commit message help
                    text
          Severity: feature
    Classification: Unclassified
                OS: All
          Reporter: self at gkayaalp.com
          Hardware: All
            Status: UNCONFIRMED
           Version: unspecified
         Component: Mercurial
           Product: Mercurial

When committing with git, one can set the `-v' or the `--verbose' flag, which
results in the patch [1] to be committed to the repository to be attached to
the commit template in unified idff format.  The patch is discarded when saving
the commit message.

*

This allows for last minute checks for confirming whether any unnecessary bits
of changes are included; and also allows for composing a better commit message
with less strain on ones short-term memory.  I can just refer to the patch [1]
while writing the message.

I have been an addict of the feature and use it with every commit I do in git. 
I use git mostly at work, and hg for my own code, and feel the lack of the
feature every time I commit.

*

I also think it is apt and necessary to have a configuration option available
to set "verbose commits" as default.  Git lacks this, and I plan to take action
on that too.

*

I reckon implementing this is easy, yet, I have not been able to try
implementing due to limited free time and lack of familiarity with the
codebase.  Excuse me for the absence of a patch.

*

[1] with patch, here I mean the "difference between the current tip and the
snapshot of the working directory that will be committed to the repository". 
Note that this is not simply the output of 'hg diff' before commit takes place.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the Mercurial-devel mailing list