Differences between revisions 1 and 3 (spanning 2 versions)
⇤ ← Revision 1 as of 2015-09-25 19:45:05 →
Size: 955
Editor: Pierre-YvesDavid
Comment:
← Revision 3 as of 2015-09-25 20:18:55 → ⇥
Size: 745
Editor: Pierre-YvesDavid
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
Mercurial can store history insformation 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. 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.
Line 10: Line 12:

The '''requires file''' is a file inside the [[Repository|repository]] which is used to describe the
general format and layout of the repository. This provides a basic mechanism for introducing new
repository formats. It is only written on repository creation, for instance during init or clone.

== Known requirements ==
Line 22: Line 18:
== Producing Compatible Bundle ==

(This section is to be filled)

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
  2. Producing Compatible Bundle

1. Known Feature

  • Feature

    Introduced
    with version

    Description

    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

(This section is to be filled)

CategoryInternals

BundleFeature (last edited 2015-12-03 05:43:15 by Pierre-YvesDavid)