[thg] [ANN] TortoiseHg 1.1.5 released

[Adrian Buehlmann]

On 02.11.2010 03:23, Steve Borho wrote:
> TortoiseHg 1.1.5 is an incremental bugfix release of the stable PyGTK branch.
> 
> http://bitbucket.org/tortoisehg/stable/wiki/ReleaseNotes#tortoisehg-115
> http://tortoisehg.bitbucket.org/download/index.html
> 
> 1.1.5 is primarily a vehicle for delivering Mercurial 1.7 to Windows
> users, though it also contains a couple of useful hgtk bug fixes.  In
> particular, it fixes a long standing bug that caused the merge and
> settings tools to try many times to detect merge tools.
> 
> The PyQt port of TortoiseHg (aka: 2.0) is coming along very nicely,
> but is not yet ready for general release.  The current plan is to
> release at the same time as Mercurial 1.8 in four months.  You can
> follow development at http://bitbucket.org/tortoisehg/thg/wiki/Home
> 
> Binary packages which can upgrade stable branch installs can be found
> at http://bitbucket.org/tortoisehg/thg/downloads.  Stable branch
> installers can (in return) upgrade these PyQt packages to bring you
> back to a stable PyGtk based install, so it's relatively painless to
> give it a test-drive.
> 

Please note that Mercurial 1.7 by default creates backward incompatible
local repositories (on 'hg init' and on 'hg clone' when using the pull
protocol).

Mercurial 1.6.X and older might not be able to read a repository created
by Mercurial 1.7. If you see the error message:

  abort: requirement 'dotencode' not supported!

then you will need Mercurial 1.7 to access that local repository.

Mercurial 1.7 can be configured to use the previous repository layout by
specifying

  [format]
  dotencode=False

in your user or system-wide config file [1].

Note that this affects only local repositories. Cloning/pushing/pulling
over http/https/ssh is not affacted. You can use *any* combination of
Mercurial versions on each end of the wire.

See http://selenic.com/repo/hg/rev/34d8247a4595 for the details.

[1] http://www.selenic.com/mercurial/hgrc.5.html#format