On Sun, Jan 11, 2009 at 6:02 AM, TK Soh <[email protected]> wrote:
> On Sun, Jan 11, 2009 at 10:23 AM, Abdul Halim <[email protected]>
> wrote:
> > Hi TK.
> >
> > I understand the risk of using a new installer for the upcoming release.
> >
> > Is it possible for the upcoming release to include the latest patches of
> qct
> > since it is still the default commit tool of tortoisehg?
>
> Let's what Steve has to say about this. I know he made some comment on
> Mercurial mailing list about making the internal commit tool default.
> Not sure if he meant to do so in 0.6.
I think it's time to make the internal commit dialog the default for new
installs.
By 0.7 we'll hopefully have a record/shelve dialog and then we can unbundle
Qct.
But there's no reason not to update the patch queue to the Qct source tip
for 0.6.
--
Steve
PS: I suspect that installing Qct separately would fix a lot of the strange
lockup bugs people report. I think those are caused by PyGtk and PyQt
fighting each other in the same process.
------------------------------------------------------------------------------
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
