allow to specify bundle type

[Benoît Allard]

> 
>>> attached a test script and output
>>
>> Sorry to ask, but ... I don't see the point in that testcase ??? The 
>> one used with --type are all aborting ... is that testing the added 
>> parameter ?
> 
> well, the test script create a bundle w/o given its type and imports it 
> again in another repo; then it creates bundles with all known types and 
> imports them again
> finally, it tries to import garbage (not a bundle) and checks if the new 
> -t option properly rejects an unknown bundle type

Don't take me wrong, but in the output you sent, there are lot of 
"abort" showing that the second part of your testsuite is not doing what 
you intended it to do ...

---
HG10BZ
abort: repository default-push not found!
abort: repository ../bHG10BZ not found!
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
HG10GZ
abort: repository default-push not found!
abort: repository ../bHG10GZ not found!
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
HG10UN
abort: repository default-push not found!
abort: repository ../bHG10UN not found!
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
---

Actually, there is a typo in the testsuite, the variable $i is used 
without being initialised ... I guess you meant $t ... (in `hg bundle -t 
$i ../b$t ../t$t`), thus shifting the parameters, and then taking ../b$t 
as type and ../t$t as bundle name producing the weird output.




-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 4197 bytes
Desc: S/MIME Cryptographic Signature
Url : http://selenic.com/pipermail/mercurial-devel/attachments/20080423/83141c59/attachment.bin