Auto-refresh proposal

Qi Yang qi.yang137 at gmail.com
Thu Feb 18 12:29:48 CST 2010


> By "private", do you mean leave it as a command but don't expose it in
> the extension help?  Or take it out of the command table entirely and
> just leave it as an internal implementation detail?

I meant to use it as an internal implementation detail.


> See above.  I don't think auto-update helps.  It might even make
> things worse, since it would remove the window between "update" and
> "bfupdate" where the user can discover the problem.

I think this should be an issue for "bfupdate". We can check the bfile
status before doing
"update" and give an warning and abort. What do you think?

The main reason I propose this is so that we could easily detect if the
standin file is modified by users. If that is not necessary, I have no
problem making "auto-refresh" optional.

-Wendy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20100218/55ba3176/attachment.htm>


More information about the Mercurial-devel mailing list