Discrepancy in outputs from "hg log"

[Peter Williams]

Matt Mackall wrote:
> On Fri, 2009-06-12 at 15:28 +1000, Peter Williams wrote:
>> So, to be compatible with the Mercurial semantics, in gwsmhg I should 
>> display whatever log/incoming/outgoing report as the files in my change 
>> set summary dialogs rather than obtaining the data using other hg 
>> commands as this is what hg users will/should expect?
> 
> Not only that, but it'll be much faster.

The only time I'm noticing unacceptable speed problems is getting a full 
history for the Linux kernel (150k approx change sets) and even then 
it's not too bad i.e. about 45 seconds.  Nevertheless, I have plans to 
modify the History (to be renamed Log to match hg) so that it only 
displays the most recent few thousand change sets by default with a 
mechanism for the user to fetch more if he/she wants them.

> 
> Does 'gwsmhg' mean anything other than it's time to trade some Scrabble
> tiles?
> 

Gui for Work Space Management using HG

I tried to make it gWSMhg so that its meaning was more clear but 
sourceforge's registration process got rid of the capitals.

It's the next logical step after doing a mq back end for gquilt (which 
started as a GUI wrapper for quilt) after I realised that mq was much 
more valuable when it use was integrated with hg management of the 
sources being modified with mq.

The form of the name, i.e. the "using HG" at the end reflects the 
possibility that at some time in the future (not high in my priorities) 
back ends for other distributed SCMs with similar semantics could be 
implemented creating gwsmgit (for instance).  This is one of the reasons 
that I interface with hg at the command line level rather than loading 
hg components as modules/packages and using them directly.  But the main 
reason is that I figure that the command line interface is inclined to 
be more stable.

Naturally, I'm developing it to match the way I use hg and mq which 
means that it may not suit others but I'm very open to suggestions to 
change or add functionality.  It also means that commands that I don't 
usually use will be the last ones covered not least because I'm not sure 
what the best graphic interface for them would be -- so once again 
suggestions welcome.

Peter
-- 
Peter Williams                                   pwil3058 at bigpond.net.au

"Learning, n. The kind of ignorance distinguishing the studious."
  -- Ambrose Bierce