Mercurial > evolve
comparison CHANGELOG @ 4628:c4097632a1a3
topic: drop support for accessing csets in branch stack using bxx (issue6119)
When topic extension is enabled and we have some cset whose hash is `b1234`,
topic extension thinks that we are accessing 1234 cset in current branch stack.
However that's not the case generally. Also I am not sure many people use this
bxxx thing.
Since we have a generic sxxx way to access csets, let's drop support for
accessing csets using bxx which leads to bad behavior.
Looking at the tests, we don't show bxxx in hg stack output anymore.
I update the test to use sxxx instead of bxxxx.
| author | Pulkit Goyal <7895pulkit@gmail.com> |
|---|---|
| date | Sat, 27 Apr 2019 01:18:08 +0300 |
| parents | d314deb12f08 |
| children | b78707559f1f |
comparison
equal
deleted
inserted
replaced
| 4626:561e97db1cf7 | 4628:c4097632a1a3 |
|---|---|
| 10 (use --no-all to evolve only one) | 10 (use --no-all to evolve only one) |
| 11 * evolve: drop compatibility with 4.4 | 11 * evolve: drop compatibility with 4.4 |
| 12 * evolve: reinstalled compatibility with narrow repositories, | 12 * evolve: reinstalled compatibility with narrow repositories, |
| 13 * evolve: use "unstable" instead of "troubled" | 13 * evolve: use "unstable" instead of "troubled" |
| 14 * evolve: run multiple stabilisation in the same transaction | 14 * evolve: run multiple stabilisation in the same transaction |
| 15 * topic: drop the b# alias. It conflicted with normal hashes. | |
| 15 | 16 |
| 16 8.5.1 -- 2019-04-23 | 17 8.5.1 -- 2019-04-23 |
| 17 ------------------- | 18 ------------------- |
| 18 | 19 |
| 19 * evolve: make sure we use upstream merge code with 5.0, | 20 * evolve: make sure we use upstream merge code with 5.0, |