Mercurial > evolve
comparison README @ 1006:deba3a063c63
push: put obsmarkers in the same bundle2 than changeset
When client is Mercurial 3.1 and server have proper evolve version and both side
have bundle2 enabled, we'll includes a part containing obsolescence markers.
When obsmarkers are included to the main bundle2 push, they will failed to be
pushed if the changeset failed to be pushed (and reciprocally).
| author | Pierre-Yves David <pierre-yves.david@fb.com> |
|---|---|
| date | Fri, 25 Jul 2014 16:54:08 +0200 |
| parents | 8043ae3612e4 |
| children | 1d8ba8244001 |
comparison
equal
deleted
inserted
replaced
| 1005:4fe159fdfc4c | 1006:deba3a063c63 |
|---|---|
| 60 4.1.0 -- | 60 4.1.0 -- |
| 61 | 61 |
| 62 - amend: add -D/--current-date option | 62 - amend: add -D/--current-date option |
| 63 - amend: add -U/--current-user option | 63 - amend: add -U/--current-user option |
| 64 - evolve: add a --tool option | 64 - evolve: add a --tool option |
| 65 - push obsmarkers in the same transaction than changesets (when using hg >= 3.1 | |
| 66 and bundle2-exp is enabled) | |
| 65 | 67 |
| 66 4.0.0 -- 2014-06-03 | 68 4.0.0 -- 2014-06-03 |
| 67 | 69 |
| 68 - require Mercurial version 3.0.1 or above | 70 - require Mercurial version 3.0.1 or above |
| 69 - some compatibility fixes with future 3.1.0 | 71 - some compatibility fixes with future 3.1.0 |