[PATCH 2 of 4 V2] commit: add ui.allowemptycommit config option
Jordi Gutiérrez Hermoso
jordigh at gmail.com
Tue May 12 19:15:07 CDT 2015
On Mon, 2015-05-11 at 20:29 -0700, Durham Goode wrote:
> # HG changeset patch
> # User Durham Goode <durham at fb.com>
> # Date 1431386308 25200
> # Mon May 11 16:18:28 2015 -0700
> # Node ID 37ef345236b146ffc75a6414411ffb6bea870a74
> # Parent bb446b7270951339396e948f4e4474781d830eff
> commit: add ui.allowemptycommit config option
> This adds a config flag that enables a user to make empty commits.
> This is useful in a number of cases.
> For instance, automation that creates release branches via
> bookmarks may want to make empty commits to that release bookmark so that it
> can't be fast forwarded
Can we please say "advanced" here instead? "Fast forwarding" from git
lacks certain connotations such as consolidating divergent bookmarks,
and brings others such as the idea that moving bookmarks has something
to do with merges. As someone who routinely uses commit messages as
API documentation, I advocate for clarity.
Other than this linguistic quibble, this series seems to me to be in pretty
More information about the Mercurial-devel