summaryrefslogtreecommitdiff
path: root/t/t0011-hashmap.sh
diff options
context:
space:
mode:
authorLibravatar Johannes Schindelin <johannes.schindelin@gmx.de>2018-05-04 01:01:23 +0200
committerLibravatar Junio C Hamano <gitster@pobox.com>2018-05-06 13:21:58 +0900
commitebddf393964120628f60f6f5e435cde87cc209c6 (patch)
tree30f61534d92bd5915894064bf083097ee01cfc70 /t/t0011-hashmap.sh
parentrebase -i --root: let the sequencer handle even the initial part (diff)
downloadtgif-ebddf393964120628f60f6f5e435cde87cc209c6.tar.xz
sequencer: allow introducing new root commits
In the context of the new --rebase-merges mode, which was designed specifically to allow for changing the existing branch topology liberally, a user may want to extract commits into a completely fresh branch that starts with a newly-created root commit. This is now possible by inserting the command `reset [new root]` before `pick`ing the commit that wants to become a root commit. Example: reset [new root] pick 012345 a commit that is about to become a root commit pick 234567 this commit will have the previous one as parent This does not conflict with other uses of the `reset` command because `[new root]` is not (part of) a valid ref name: both the opening bracket as well as the space are illegal in ref names. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t0011-hashmap.sh')
0 files changed, 0 insertions, 0 deletions