http://code.google.com/p/tortoisehg-nightly/downloads/list

I've just uploaded the first functional binary installer based on the
crew repository,
i.e. this is a three-month early preview of what is coming in 0.8.
Beware that this
is for testing purposes only, please do not use this on production machines.

See the crew release notes for somewhat complete description of the changes
already on crew:

http://bitbucket.org/tortoisehg/stable/wiki/crew-release-notes

Highlights:
* New overlay and context menu code from Simon Heimberg
* New shell extension tab on global config dialog (changes take effect
after reboot)
* Diffs between revs in file log now work as expected
* commit tool has improved MQ support
* bug reporting tool for when tracebacks occur in our dialogs

Hidden changes:
* hgproc.exe is gone, we use hgtk.exe exclusively to launch dialogs
* cmenu and CLI have been standardized.  Selecting files, right-click,
select option
  is equivalent to opening shell, cd to same directory, running hgtk
'option' 'files'
* debugging in shell extensions is disabled by default.  Small perf
gain, but this
  is mostly to cut down on conflicts with other applications. (issue #67)

LowLights:
* 'hgtk vdiff' is broken in the binary installer.  This means visual
diff from the shell
context menu is also broken. This is strange because it works great
with a source
install.  Somehow mercurial is not running extdiff.uisetup() when hgtk
is an exe.
Launching vdiff from commit or log or another tool works just fine.
* app filter for the shell extensions is not implemented.

--
Steve Borho

PS: It should be safe to install this over the top of a released thg
package, though
you probably want to uninstall it manually before downgrading back to an earlier
release build just to be safe.

------------------------------------------------------------------------------
_______________________________________________
Tortoisehg-discuss mailing list
Tortoisehg-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss

Reply via email to