diff options
| author | Alan Potter <alanjpotter@gmail.com> | 2023-10-24 05:32:29 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-10-24 05:32:29 -0400 |
| commit | 4d18b62c540cf7bfe1fd89951957d73e9e70f01e (patch) | |
| tree | 164e2dd16a4bfa508d13db3ce8cc2a3da7a1b1de /docs/Stacked_Branches.md | |
| parent | 8193731a828e1c966b5a850a08f24d07db6e2f9a (diff) | |
Update Stacked_Branches.md
Fix a typo.
Diffstat (limited to 'docs/Stacked_Branches.md')
| -rw-r--r-- | docs/Stacked_Branches.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/Stacked_Branches.md b/docs/Stacked_Branches.md index b73e4aca5..3e943e791 100644 --- a/docs/Stacked_Branches.md +++ b/docs/Stacked_Branches.md @@ -7,7 +7,7 @@ refactorings, one for backend changes, and one for frontend changes. Those branches would then all be stacked onto each other. Git has support for rebasing such a stack as a whole; you can enable it by -setting the git config `rebase.updateRfs` to true. If you then rebase the +setting the git config `rebase.updateRefs` to true. If you then rebase the topmost branch of the stack, the other ones in the stack will follow. This includes interactive rebases, so for example amending a commit in the first branch of the stack will "just work" in the sense that it keeps the other |