[PATCH] merge : deprecate the --force option

Pierre-Yves David pierre-yves.david at ens-lyon.org
Thu Jul 18 05:21:56 UTC 2013


On 18 juil. 2013, at 00:01, Florence Laguzet wrote:

> # HG changeset patch
> # User Florence Laguzet <florence.laguzet at gmail.com>
> # Date 1374098284 -7200
> # Node ID 9b722d1121d852f52c453e55619a2bcefb815cb3
> # Parent  3185b347ae9829ea275973f65460539fa01f36f6
> merge : deprecate the --force option
> 
> The --force option in merge does not make what people think it does so it may
> not be visible to everyone.
> 
> I have local changes and want to pull one's changes which made 2 heads.
> The --force option in help says
> " -f --force  force a merge with outstanding changes"
> so I can expect that I can use it to force the merge and commit it in
> my local repository without taking my local changes into account.
> But merging with -f keeps local changes and "add" them : they must be committed
> or reverted before doing the merge commit.
> The merge -f cannot be  reverted so it leads my repository in a bad state :
> cannot commit  merge and don't want to revert/commit local changes yet.

+1 I can't see a sensible use case for that flag and I've seen multiples people coming from svn tricked into using this flag. They get in pretty nasty situation as they usually does not know how to abort the merge at all (using hg update --clean) and are forced to either abandon their repository or commit unwanted changes.

-- 
Pierre-Yves David


More information about the Mercurial-devel mailing list