On 05.05.2008 06:12, Steve Borho wrote: > 0.4 RC2 is now uploaded on SourceForge.
Thanks Steve for your work. I do have a concern with RC2: RC2 uses 626cb86a6523 of Mercurial, which is only available from the Mercurial _crew_ repo. 368a4ec603cc in RC2 (from hg main repo) breaks imerge (see the notes section on ImergeExtension in Mercurial wiki): http://selenic.com/repo/index.cgi/hg/rev/368a4ec603cc http://www.selenic.com/mercurial/wiki/index.cgi/ImergeExtension Imerge is distributed with Mercurial. Shipping a broken extension with Mercurial seems a bit odd. RC2 includes 92ccccb55ba3: http://selenic.com/repo/index.cgi/hg/rev/92ccccb55ba3 ''' changeset: 6518:92ccccb55ba3 user/date: Matt Mackall <[EMAIL PROTECTED]> 2008-04-11 17:52:56 resolve: new command - add basic resolve command functionality - point failed update and merge at resolve ''' While this seems to be a nice new feature and possibly helps around that broken imerge, it is rather new, undocumented (Mercurial wiki), untested and thus potentially unstable (in the sense that its externally observable behaviour could change until the next official Mercurial release). I'm not strictly against including 92ccccb55ba3, but I asked myself whether it is wise to include it in a new official release of TortoiseHG (TortoiseHG as a guinea-pig?). An alternate solution might be to use the tip of http://selenic.com/repo/hg-stable for rc2, which does not include csets 368a4ec603cc, 92ccccb55ba3. I'm uncertain on this myself. Just wanting to point this out. ------------------------------------------------------------------------- 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-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
