[PATCH] merge: Be precise about what merged into what in short desc

Pierre-Yves David pierre-yves.david at ens-lyon.org
Wed Nov 26 14:23:38 CST 2014



On 11/26/2014 12:09 PM, anatoly techtonik wrote:
> On Wed, Nov 26, 2014 at 10:50 PM, Matt Mackall <mpm at selenic.com> wrote:
>> On Wed, 2014-11-26 at 17:22 +0300, anatoly techtonik wrote:
>>> # HG changeset patch
>>> # User anatoly techtonik <techtonik at gmail.com>
>>> # Date 1417011729 -10800
>>> #      Wed Nov 26 17:22:09 2014 +0300
>>> # Branch stable
>>> # Node ID ef7bd889ba988435ce87fceb9a1bb72c46a97e9b
>>> # Parent  6dfb78f18bdba03067c7060cbe5b4ca2e757dde9
>>> merge: Be precise about what merged into what in short desc
>>
>> Queued for stable, thanks. Caps fixed in flight.
>
> Sorry for caps - too many projects and conventions to remember and too
> little time to reread the docs. This requirement from
> http://mercurial.selenic.com/wiki/ContributingChanges is quite easy to
> check with script, but that doesn't work for emailing changes and for
> cloned repositories. What is the best practice to preserve project
> safety harness while cloning?

The test-check-*.t series of test will validate the Mercurial code 
style. One of them check for commit message too.

-- 
Pierre-Yves David


More information about the Mercurial-devel mailing list