"hg up -C" is also evil - ;-)

[Waldemar]

On 11/05/2010 07:55 AM, Kevin Bullock wrote:
> On 5 Nov 2010, at 7:12 AM, Marko Käning wrote:
>
>   
>> Yesterday I issued the command
>>
>> 	$ hg up -C
>>
>> actually believing that local changes would be moved into *.orig prior to 
>> the clean update of my working copy.
>>
>> But I was wrong! In many other cases local changes will be preserved with 
>> *.orig files or additional warning messages will be thrown, but obviously 
>> not with a clean update...
>>     
> -C == --clean, which would indicate to me that any uncommitted work will at least be at _risk_ of disappearing. It would seem to make sense to write *.orig files though.
>
> pacem in terris / mir / shanti / salaam / heiwa
> Kevin R. Bullock
>   

I think what's missing is a really solid integration with "shelve".   In
case of hg update, working directory should ideally be stored in some
orderly manner with a chance of quick restoration with a single
command.  For me it's the "third level" of source control. After
traditional versioning, mq patches, this would be workdir management.

In case of purge, it should just do what it says: purge.  I find purge
extremely useful when debugging builds.  It gets rid of transient files
and allows me to rerun makefiles with confidence.

>   
>> Is this intentional?
>> _______________________________________________
>> Mercurial mailing list
>> Mercurial at selenic.com
>> http://selenic.com/mailman/listinfo/mercurial
>>     
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
>