Mercurial > hg
comparison relnotes/next @ 44555:05654ea5137c
rebase: accept multiple --source arguments (BC)
I think it's a little surprising that `hg rebase -s A -s B` rebases
only `B::` and ignores `A`. That's because the `-s` flag is not a
repeated flag. This patch makes it a repeated flag.
Differential Revision: https://phab.mercurial-scm.org/D8292
author | Martin von Zweigbergk <martinvonz@google.com> |
---|---|
date | Fri, 13 Mar 2020 16:39:32 -0700 |
parents | bd7b2c8d06cc |
children | f63598aa1c4b |
comparison
equal
deleted
inserted
replaced
44554:c4c97cabfc16 | 44555:05654ea5137c |
---|---|
56 * When `hg rebase` pauses for merge conflict resolution, the working | 56 * When `hg rebase` pauses for merge conflict resolution, the working |
57 copy will no longer have the rebased node as a second parent. You | 57 copy will no longer have the rebased node as a second parent. You |
58 can use the new `conflictparents()` revset for finding the other | 58 can use the new `conflictparents()` revset for finding the other |
59 parent during a conflict. | 59 parent during a conflict. |
60 | 60 |
61 * `hg rebase` now accepts repeated `--source` arguments. For example, | |
62 `hg rebase --source 'A + B'` is equivalent to `hg rebase --source A | |
63 --source B`. This is a backwards-incompatible change because it | |
64 will break overriding an alias `myrebase = rebase --source A` by | |
65 `hg myrebase --source B` (it will now rebase `(A + B)::` instead of | |
66 `B::`). | |
67 | |
61 * `hg recover` does not verify the validity of the whole repository | 68 * `hg recover` does not verify the validity of the whole repository |
62 anymore. You can pass `--verify` or call `hg verify` if necessary. | 69 anymore. You can pass `--verify` or call `hg verify` if necessary. |
63 | 70 |
64 * `hg debugmergestate` output format changed. Let us know if that is | 71 * `hg debugmergestate` output format changed. Let us know if that is |
65 causing you problems and we'll roll it back. | 72 causing you problems and we'll roll it back. |