|
Size: 745
Comment:
|
← Revision 4 as of 2015-12-03 05:43:15 ⇥
Size: 1228
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 20: | Line 20: |
| (This section is to be filled) | You can convert bundle from one format to another using: {{{ cd yourepository/ hg bundle --rev 'bundle()' --base 'parents(roots(bundle()))' -R EXISTINGBUNDLE NEWBUNDLE --type NEWFORMAT }}} (Yep, this is awful and we should improve that command line ergonomic) Here is a list of useful type of bundle as in latest Mercurial release. See `hg help bundle` for details about the `--type` argument. || Type || feature || || v1 || HG10 || || none-v2 || HG20 || || v2 || HG20+Compression || |
Bundle File
All about handling unknown feature in bundle.
Mercurial can store history information into "bundle file" for sharing or backup purpose. The format and feature of these bundle evolve over time in a way that can make new client produce bundle that and older client cannot read.
Contents
1. Known Feature
Feature
Introduced
with versionDescription
HG10
0.7
the good old historical format for mercurial bundles
HG20
3.5
A more extensible bundle format
Compression
3.6
compression for HG20 bundle
2. Producing Compatible Bundle
You can convert bundle from one format to another using:
cd yourepository/
hg bundle --rev 'bundle()' --base 'parents(roots(bundle()))' -R EXISTINGBUNDLE NEWBUNDLE --type NEWFORMAT(Yep, this is awful and we should improve that command line ergonomic)
Here is a list of useful type of bundle as in latest Mercurial release. See hg help bundle for details about the --type argument.
Type
feature
v1
HG10
none-v2
HG20
v2
HG20+Compression