QT4 has a QT3 "compatability layer". there's even a qt3to4 tool which looks at the source code and mutates all the QT3 calls to QT4 calls. It works quite well Yaron On 7/25/06, Barry Smith <[email protected]> wrote:

Satish,

Your proposed solution is ridiculously cumbersome; no sane person would put up with that nonsense.

If the authors of the ct would get their heads out of their asses and update it to Qt4 (which is like, what, a year old) instead of the outdated Qt3 maybe people who use updated software could use it.

Barry

On Tue, 25 Jul 2006, Satish Balay wrote:

...

On Tue, 25 Jul 2006, Barry Smith wrote:

...

On Tue, 25 Jul 2006, Satish Balay wrote:

...

Yes - not having file comments makes it more difficult to go back in file history.

But one way to look at it is - for some of these senarios - it meanas multiple changesets should be created [with the correct grouping of changes] instead of the atempted single changeset.

Yes, the problem with this is that there is no decent way of making multiple change-sets.

- quit emacs without typing in any comments [so no commit is done] - 'hg status' to get the list of modified files - hg commit file1 file2 [ to make the appropriate changeset]

I use 'hg ct' though..

...

If I could just edit out the files I did not want when doing the comment for a commit it would make life a MILLION times better (could that be added?).

I'll check on this on the mercurial list..

Satish

...

Barry

...

And perhaps some comments can actually go into the code.

Satish

On Tue, 25 Jul 2006, Barry Smith wrote:

...

Not having file by file comments for changesets is starting to annoy me.

Barry