On Wed, Apr 9, 2008 at 1:07 AM, Ted Pavlic <[EMAIL PROTECTED]> wrote: > > I've just uploaded a release candidate installer for 0.4 to > > sourceforge. This is _not_ an official release, and there will likely > > be an RC2 before the official release is made. There's been a lot > > of changes since 0.3 that we would like tested before the official > > release is launched (not the least of which were the dozens of > > changes in hg-1.0). > > In Synchronize, when both "do fetch" and "update to new tip" in the > little box, shouldn't the "update to new tip" be applied first? > > Right now, if BOTH are checked, fetch dies staying that the working > directory needs to be updated to the tip. > > Thoughts?
The "update to new tip" is meant to take effect after pulling, i.e. hg pull --update. But Fetch expects the repo to be at tip. I guess we can make the options mutually exclusive if necessary. TK ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Tortoisehg-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
