win32 tool bundling progress

[Steve Borho]

I've made quite a bit of progress on the "Batteries Included" win32 
bundle patch queue, and would like to generate an installer for people 
to test drive so I can get some feedback.  However there's a couple of 
details I would like some guidance about before making an installer 
generally available.

* What should my annotated installer report when the user runs "hg 
version"?  Since my changes are in a patch queue, the hash of my 
working directory does not correspond to any changeset in the source 
repository.  Should I just hard-code the hash of qparent?  Or would you 
prefer I add some annotation to the hash to imply it's a non-standard 
build, like say:  
	Mercurial Distributed SCM (version bbdcdc7f170e+win32extras)

* Building this patch queue that has a binary file in it has exposed a 
flaw in qct's handling of qrefresh.  There's currently no way to tell 
qct to use --git, and I can't figure out any foolproof heuristics for 
setting it internally.  A user could put --git in his defaults if they 
knew it was necessary, and I'm tempted to just leave it at that.

-- 
Steve Borho (steve at borho.org)
http://www.borho.org/~steve/steve.asc
Key fingerprint = 2D08 E7CF B624 624C DE1F  E2E4 B0C2 5292 F2C6 2C8C