How to spot a clean/non-clean Mercurial update

[Boggess, Rod]

It's not perfect, but you can create a hook to shelve, update, and unshelve.

Sent from my Motorola Smartphone on the Now Network from Sprint!

-----Original message-----
From: Peter Toft <pto at linuxbog.dk>
To: Mads Kiilerich <mads at kiilerich.com>
Cc: Mercurial <mercurial at selenic.com>
Sent: Thu, Dec 13, 2012 13:49:01 EST
Subject: Re: How to spot a clean/non-clean Mercurial update

Den 2012-12-13 00:54, Mads Kiilerich skrev:
> Peter Toft wrote, On 12/12/2012 02:55 PM:
>
>> Hi again I need your help to predict whether a "hg pull -u" will >> give  
a
>> clean update or not.
>
> A hack like
> hg diff -r.:tip | patch --dry-run --forward
> might give a useful approximation in most cases.
>
> A better answer is this: You should never make an update with
> uncommitted changes in the working directory. If you follow that > advice
> then you know that the working directory is clean and the update will > be
> smooth.
>
> /Mads

Perfect Mads (again) - thanx a mil!

Even though I understand the "never update with uncomitted changes" - this
might not be easy for me, but that part we can discuss over a beer some day
:)

/pto

-- Peter Toft, PhD
http://petertoft.dk
_______________________________________________
Mercurial mailing list
Mercurial at selenic.com
http://selenic.com/mailman/listinfo/mercurial

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20121213/c766bc43/attachment-0002.html>