[BUG] The -f option to qnew has been removed

[Augie Fackler]

On Nov 18, 2010, at 7:39 PM, Peter Williams wrote:

> The behaviour of qnew no longer conforms to the description on page  
> 235 of "Mercurial, The Definitive Guide" due to the removal of the - 
> f option to this command.

The book is currently at least 3 major versions of Mercurial out of  
date, I think it actually dates back to 1.2.

> This is a bad thing as it allows a user to inadvertently create a  
> new patch that contains changes that were intended for the current  
> patch if they forget to do a qrefresh before creating the new patch.
>
> The original behaviour, that required the -f flag to be used if the  
> user intended any outstanding changes to be included in the new  
> patch, is considered (by me) to be superior to the new behaviour as  
> it provides the user with more flexibility and defends against  
> unintended consequences.

We had a long talk about this in February at the 1.5 sprint and nobody  
present liked the old behavior of qnew. We changed the behavior of  
qnew at that time and -f has been a noop since 1.6 (and I believe was  
listed as deprecated.)

>
> Peter
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at selenic.com
> http://selenic.com/mailman/listinfo/mercurial-devel