On Wed, Jan 7, 2009 at 2:24 AM, Arne Babenhauserheide <[email protected]>wrote:
> Also Qct didn't work for another friend of mine (locked the repo and never
> let
> go), so I had to reset the config to the standard tool. Sticking to the
> simple
> dialog and only offering Qct as option would have avoided quite many
> problems
> for us. The first impression was "damn, the repo's stuck - let's clone it
> again"
Do you have any more information about what THG release this was, and what
operation caused it to hang? There was a problem a few releases ago with
large commits. Qct was printing the list of committed files to stdout, and
in that python/qt environment on Windows that caused some queue somewhere to
fill up and block with no recourse. This has been addressed in later
release (by trimming the print statements).
It's our long-term goal to get the internal tool feature-complete so that we
don't need to ship Qct anymore (since everything else in THG uses GTK). I
think we're getting pretty close to that goal. Perhaps in the next release
we can make the internal tool the default for new installs.
--
Steve
------------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
_______________________________________________
Tortoisehg-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
